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

Re: [RFH] An early draft of v1.5.0 release notes

From
Jakub Narebski <jnareb@gmail.com>
Date
Dec 27, 2006, 10:12 UTC
Message-ID
<emtgps$f1q$1@sea.gmane.org>
In-Reply-To
<7vvejx948y.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> This is still rough, but I think we have a pretty good idea what
> will and what won't be in v1.5.0 by now, and end-of-year is a
> good slow time to summarize what we have done.

Very nice idea! Perhaps those release notes can find it's way into either v1.5.0 commit, or v1.5.0 tag comment?

Just a few comments:
Show 5 quoted lines
>  - git-add without any argument does not add everything
>    anymore.  Say "git add ." if you want to.
> 
>  - git-add tries to be more friendly to users by offering an
>    interactive mode.
Perhaps information that git-add can be used to add ignored files
with -f option should be added? Or is it not important enough?
 
Show 10 quoted lines
>  - The commits referred to by reflog entries are now protected
>    against pruning.  The new command "git reflog expire" can be
>    used to truncate older reflog entries and entries that refer
>    to commits that have been pruned away previously.
> 
>    Existing repositories that have been using reflog may get
>    complaints from fsck-objects; please run "git reflog expire
>    --all" first to remove reflog entries that refer to commits
>    that are no longer in the repository before attempting to
>    repack it.
That's a bit bad, as it forces to lose some info... but that
info was not that useful anyway.
 
Show 5 quoted lines
>  - A commit object recorded in non UTF-8 encoding records the
>    encoding i18n.commitencoding specified in the originating
>    repository in a new "encoding" header.  This information is
>    used by git-log and friends to reencode the message to UTF-8
>    when displaying.
I don't quite like it. Why if someone uses different encoding
that utf-8 because his terminal is not set to utf-8? Having suddenly
what looks like garbage on output, while input was in local encoding
(and specified in i18n.commitencoding) is a bit suprising...
 
> ----------------------------------------------------------------
> (shortlog since v1.4.4.3 here)
I'd rather have description a la "what's cooking" here... 
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Shawn PearceNext: Junio C Hamano
Message 3 of 20 in “[RFH] An early draft of v1.5.0 release notes”
  1. Junio C HamanoDec 27, 2006
  2. Shawn PearceDec 27, 2006
  3. Jakub NarebskiDec 27, 2006
  4. Junio C HamanoDec 27, 2006
  5. Johannes SchindelinDec 27, 2006
  6. Jakub NarebskiDec 27, 2006
  7. Jakub NarebskiDec 27, 2006
  8. Junio C HamanoDec 27, 2006
  9. Jakub NarebskiDec 28, 2006
  10. Junio C HamanoDec 27, 2006
  11. An early draft of v1.5.0 release notes (2nd ed)Junio C Hamano, Dec 28, 2006
  12. Shawn PearceDec 28, 2006
  13. Junio C HamanoDec 28, 2006
  14. Shawn PearceDec 28, 2006
  15. Junio C HamanoDec 28, 2006
  16. Shawn PearceDec 28, 2006
  17. Junio C HamanoDec 28, 2006
  18. Junio C HamanoJan 10, 2007
  19. Eric WongDec 28, 2006
  20. Junio C HamanoDec 28, 2006

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.