Re: [PATCH] doc: explain why file: URLs and bundles don't mix

> > +- When cloning, the former implies --local option. See > > + linkgit:git-clone[1] for details. > > + > > +- The latter is implemented using linkgit:git-upload-pack[1], which > > + expects its repository to be a directory, and therefore does not > > + work for bundles (see linkgit:git-bundle

[PATCH] doc: explain why file: URLs and bundles don't mix

Signed-off-by: Alyssa Ross --- Documentation/urls.txt | 20 +++- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/Documentation/urls.txt b/Documentation/urls.txt index b05da95788..c83d9f859e 100644 --- a/Documentation/urls.txt +++ b/Documentation/urls.txt @@ -43,14

Re: Recovering from a "detached from" HEAD

> The commit the message shows is meant to indicate where your unnamed > branch diverged at named branches. Immediately after moving to the > unnamed branch by detaching the HEAD, the message says "at"; the > HEAD is pointing directly at the tip of the then-current branch and > that is where the t

Recovering from a "detached from" HEAD

If I detach my head, then use `git subtree add` to generate a commit, the output from `git status` changes from "detached at SHA" to "detached from SHA". The sha doesn't change, but HEAD has updated. I don't understand why `git status` doesn't tell me that I'm "detached at" the sha of the new comm