![]() This is a public inbox, see mirroring instructionsįor how to clone and mirror all data and code used for this inbox Īs well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s). * If your mail client supports setting the In-Reply-To headerīe sure your reply has a Subject: header at the top and a blank lineĬode repositories for project(s) associated with this public inbox * Reply using the -to, -cc, and -in-reply-to * Save the following mbox file, import it into your mail client,Īvoid top-posting and favor interleaved quoting: You may reply publicly to this message via plain-text email 4:08 ` RF+ENH(TST): compare the entire list of submodule status -recursive to stay intact Yaroslav Halchenko 4:08 ` submodule: Add -reset-hard option for git submodule update Yaroslav Halchenko 17:35 git submodule update -reset-hard Yaroslav Halchenko Thread overview: 18+ messages / expand mbox.gz Atom feed top Submodule branch is out of sync with the superprojectĪdding another mode to `git submodule update` sounds Would you typically have situations where the When set would not detach HEAD in submodules.Ĭan you say more about the first question above: You may be interested introduces a switch `submodule.repoLike `, which Git submodule foreach -recursive git reset -hard > "were in"? reflog records might have that information) > What I want is to retain current branch they are at (or may be possible ![]() > I would end up in the detached HEADs within submodules. The above reset with `-recurse` would fix) or changed the branch Undesirable in the sense of still having local changes (that is what But that leaves all the submodules now in > there is a need to just "forget" some changes. > the entire tree of them stays in a "clean" state. > doing all necessary commits in the repositories leading to that submodule so while committing changes within deep submodule, while also > single command could introduce a good number of commits across deep hierarchy ![]() If you need to reset the whole repository to. > easy ways to do some manipulations across full hierarchies of them. First, you have to use git clean -f -d to get rid of untracked files and directories in your working copy. > Rationale: In DataLad we heavily rely on submodules, and we have established What if the branch differs from the sha1 recorded in the superproject? > checks out necessary commit, but I want it to remain in the branch. While submodules are useful for a few use cases, they do have several drawbacks. git submodule update -recursive > I would end up in the detached HEADs. Tutorials Git subtree: the alternative to Git submodule Nicola Paolucci The Internet is full of articles on why you shouldn’t use Git submodules. > -reset-hard option, which would be very similar to regular "update" which > git reset -hard PREVIOUSSTATE git reset. > I wondered what would be your take on my wishlist request to add On Thu, at 10:02 AM Yaroslav Halchenko wrote: Subject: Re: git submodule update -reset-hardĭate: Thu, 10:29:28 -0800 Re: git submodule update -reset-hard - Stefan Beller mailing list mirror (one of many) help / color / mirror / code / Atom feed From: Stefan Beller
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |