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

Re: What's cooking in git.git (topics)

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Mar 4, 2007, 12:32 UTC
Message-ID
<Pine.LNX.4.63.0703041321290.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<7v7itx5mep.fsf@assigned-by-dhcp.cox.net>
Hi,
On Sun, 4 Mar 2007, Junio C Hamano wrote:
Show 5 quoted lines
> * js/attach (Sun Mar 4 00:12:06 2007 +0100) 1 commit
>
> [...]
>
> * js/symlink (Sat Mar 3 20:38:00 2007 +0100) 3 commits
The prefix system is showing its limitation... :-)
Show 5 quoted lines
> * js/gnucl (Fri Mar 2 15:29:08 2007 +0100) 2 commits
>  - --pretty=gnucl: avoid line wrapping before the comma
>  - Add --pretty=gnucl
> 
> This is to output logs in the GNU ChangeLog format.

FWIW I am opposed to include that. After letting it sink in, Linus' remarks convinced me that this format is not as useful as our other log formats, and for those people who really want it, there is git2cl.

> * js/revert-cherry (Thu Mar 1 05:26:30 2007 +0100) 1 commit
>  + Make git-revert & git-cherry-pick a builtin
> 
> Will cook for some time.

Yes. I worked with them a bit, but nowhere enough to say that they are not introducing regressions.

Show 8 quoted lines
> * js/diff-ni (Sun Feb 25 23:36:53 2007 +0100) 4 commits
>  + Get rid of the dependency to GNU diff in the tests
>  + diff --no-index: support /dev/null as filename
>  + diff-ni: fix the diff with standard input
>  + diff: support reading a file from stdin via "-"
> 
> I've fixed up this series since it was posted, and I think it is
> in a testable shape now, so it is in 'next'.
Thank you.
Show 7 quoted lines
> * js/fetch-progress (Sun Feb 25 13:13:17 2007 -0800) 3 commits
>  . git-fetch: add --quiet
>  + Fixup no-progress for fetch & clone
>  + fetch & clone: do not output progress when not on a tty
> 
> The early parts that have been in 'next' should be ready to go to 
> 'master' now.  The last one I am not sure.

BTW I just added this to my fetches in crontab: ' | sed -e "s/^.*\r//g"' This is the workaround Nico proposed, only a little bit more obvious (and removable).

Ciao, Dscho

Previous: Junio C HamanoNext: Linus Torvalds
Message 9 of 28 in “What's cooking in git.git (topics)”
  1. Junio C HamanoFeb 20, 2007
  2. Eric WongFeb 20, 2007
  3. Junio C HamanoFeb 20, 2007
  4. Alexander LitvinovFeb 20, 2007
  5. Junio C HamanoFeb 23, 2007
  6. Johannes SchindelinFeb 23, 2007
  7. Junio C HamanoFeb 23, 2007
  8. Junio C HamanoMar 4, 2007
  9. Johannes SchindelinMar 4, 2007
  10. Linus TorvaldsMar 4, 2007
  11. Junio C HamanoMar 4, 2007
  12. Marco CostalbaMar 4, 2007
  13. Junio C HamanoMar 13, 2007
  14. Matthias LederhoferMar 13, 2007
  15. Junio C HamanoMar 13, 2007
  16. Matthias LederhoferMar 13, 2007
  17. Julian PhillipsMar 13, 2007
  18. Junio C HamanoMar 13, 2007
  19. Santi BéjarMar 13, 2007
  20. Junio C HamanoMar 14, 2007
  21. Santi BéjarMar 14, 2007
  22. Junio C HamanoMar 25, 2007
  23. Johannes SchindelinMar 25, 2007
  24. Junio C HamanoMar 25, 2007
  25. Johannes SchindelinMar 25, 2007
  26. Florian WeimerMar 26, 2007
  27. Junio C HamanoMar 26, 2007
  28. Document git-log --first-parentJunio C Hamano, Mar 27, 2007

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.