![]() It does not push the change to Github # more work # another commit it is VERY fast to commit # NOTE: doing a commit is a local operation. # Add all files to be committed ``git add -u`` will add all modified (but not untracked) # See what files have been modified or added # the -b requests that the branch be created # ``git branch`` will list all the branches you have checked out locally at some point # ``git branch -a`` will list all branches in repository (checked out or not) # work work work 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).# master is the 'trunk' and main development branch # the checkout command "checks out" the requested branch 10:50 Wanted: shallow submodule clones with -no-single-branch Tor AnderssonĬode repositories for project(s) associated with this public inbox links below jump to the message on this page. Thread overview: 2 messages (download: mbox.gz / follow: Atom feed) To support direct sha1s unlike the update command?Įnd of thread, other threads: $branch and record that, so I do not see the need in the add code In "submodule add" I think it is sufficient to take the current remotes "submodule update" tries to fetch by sha1ĭirectly in the hope that the server has uploadpack.\ I think fixing the branch option comes a bit closer, but still doesn'tįix this root problem. > retrieve and graft the actual commit the submodule points to, but > Better yet would be for the shallow submodule clone to automatically ![]() So adding it unconditionally is a bad idea IMHO, we'd need to have a flagįor that propagated from git-submodule.sh (function cmd_add) to the Least amount of data, which is why -depth implies -single-branch Well, when asking for depth=1, the user usually actually wants to have the > if this will have any other adverse effects? > builtin/submodule-helper.c clone_submodule function, but I'm not sure > patch to hardwire the -no-single-branch argument in the fixing the -branch flag sounds like the right approach for this > tag or branch without ending up in this situation.Īdding -no-single-branch sounds like a good idea for general use,īut it seems like a clunky workaround when looking for a specific branch, > the submodule clone process, since then a submodule can point to any ![]() > It would be useful if I could pass the -no-single-branch argument to This however doesn't clone the correct branch. You can also use the "-branch=not_master" flag to track another branch. This often leaves the submodule pointing to a non-existing > When adding submodules with -depth=1 only the master branch is 10:50 Wanted: shallow submodule clones with -no-single-branch Tor 19:21 ` Stefan Beller 0 siblings, 0 replies 2 messages in threadįrom: Stefan Beller 19:21 UTC ( / raw) ![]() * Re: Wanted: shallow submodule clones with -no-single-branch. Retrieve and graft the actual commit the submodule points to, but If this will have any other adverse effects?īetter yet would be for the shallow submodule clone to automatically Patch to hardwire the -no-single-branch argument in theīuiltin/submodule-helper.c clone_submodule function, but I'm not sure Tag or branch without ending up in this situation. The submodule clone process, since then a submodule can point to any It would be useful if I could pass the -no-single-branch argument to When adding submodules with -depth=1 only the master branch isĬloned. 19:21 ` Stefan Beller 0 siblings, 1 reply 2 messages in threadįrom: Tor Andersson 10:50 UTC ( / raw) mailing list mirror (one of many) help / color / mirror / code / Atom feed * Wanted: shallow submodule clones with -no-single-branch. Wanted: shallow submodule clones with -no-single-branch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |