git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH,v2] git-bundle(1): add no references required simplest case

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 2, 2009, 00:04 UTC
Message-ID
<alpine.DEB.1.00.0902020056520.3586@pacific.mpi-cbg.de>
In-Reply-To
<87pri12078.fsf@jidanni.org>
Hi,
On Mon, 2 Feb 2009, jidanni@jidanni.org wrote:
Show 6 quoted lines
> Words totally by Junio C Hamano.
> Signed-off-by: jidanni <jidanni@jidanni.org>
> ---
> 
> Junio: I used your words.
> You might have missed this patch. Resending.

You are not serious, are you? People have explained time and time again what is required by a commit message.

Now, I am not a native speaker, but the commit subject seems to contain grammatical errors. Even if it weren't, it is not understandable.

So the only thing that is in your complete commit message remotely purporting to explain what the patch is about and why it is good, fails to do so.

Also, we always have an empty line before SOB lines.
> +A complete bundle is one that does not require you to have any

I have not heard of any "complete" bundle before, and I do not understand the need for such a definition, either.

> +prerequisite object for you to extract its contents.  Not only you
> +can fetch/pull from a bundle, you can clone from a complete bundle
"Not only you can" violates grammar in my book.
Show 12 quoted lines
> +as if it was a remote repository, like this:
> +
> +----------------
> +$ git clone /home/me/tmp/file.bdl mine.git
> +----------------
> +
> +This will define a remote called "origin" in the resulting
> +repository that lets you fetch and pull from the bundle, just
> +like the previous example lets you do with the remote called
> +"bundle", and from then on you can fetch/pull to update the
> +resulting mine.git repository after replacing the bundle you store
> +at /home/me/tmp/file.bdl with incremental updates.

IMO this paragraph just adds words, not anything the user does not know already by that stage.

Ciao, Dscho

Previous: jidanni@jidanni.orgNext: Junio C Hamano
Message 24 of 32 in “How to extract files out of a "git bundle", no matter what?”
  1. jidanni@jidanni.orgDec 19, 2008
  2. Shawn O. PearceDec 19, 2008
  3. Mark LevedahlDec 19, 2008
  4. jidanni@jidanni.orgDec 19, 2008
  5. Jeff KingDec 19, 2008
  6. jidanni@jidanni.orgDec 19, 2008
  7. Jeff KingDec 19, 2008
  8. Documentation/git-bundle.txt: Dumping contents of any bundlejidanni@jidanni.org, Jan 1, 2009
  9. Johannes SchindelinJan 1, 2009
  10. Jeff KingJan 1, 2009
  11. jidanni@jidanni.orgJan 1, 2009
  12. Jeff KingJan 1, 2009
  13. jidanni@jidanni.orgJan 2, 2009
  14. Shawn O. PearceJan 2, 2009
  15. Jeff KingJan 2, 2009
  16. jidanni@jidanni.orgJan 2, 2009
  17. git ls-tree prints wacko file sizes if it can't find the blobjidanni@jidanni.org, Jan 1, 2009
  18. jidanni@jidanni.orgJan 1, 2009
  19. Handle sha1_object_info failures in ls-tree -lAlex Riesen, Jan 1, 2009
  20. git-bundle(1): add no references required simplest casejidanni@jidanni.org, Jan 26, 2009
  21. Junio C HamanoJan 26, 2009
  22. git-bundle(1): add no references required simplest casejidanni@jidanni.org, Jan 29, 2009
  23. jidanni@jidanni.orgFeb 1, 2009
  24. Johannes SchindelinFeb 2, 2009
  25. Junio C HamanoFeb 2, 2009
  26. jidanni@jidanni.orgFeb 4, 2009
  27. Junio C HamanoFeb 4, 2009
  28. jidanni@jidanni.orgFeb 4, 2009
  29. git-bundle doc: update examplesNanako Shiraishi, Feb 4, 2009
  30. Jeff KingFeb 4, 2009
  31. Junio C HamanoFeb 4, 2009
  32. Junio C HamanoDec 19, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.