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

Re: GIT - breaking backward compatibility

From
Petr Baudis <pasky@suse.cz>
Date
Sep 20, 2005, 13:23 UTC
Message-ID
<20050920132351.GB1884@pasky.or.cz>
In-Reply-To
<7vpsr4cx0f.fsf@assigned-by-dhcp.cox.net>

Dear diary, on Tue, Sep 20, 2005 at 04:07:28AM CEST, I got a letter where Junio C Hamano <junkio@cox.net> told me that...

> I raised the following issues in my previous messages but did
> not hear many opinions [*1*].  I do not want to take it as a
> blank check from the community to do whatever I please.  So here
> is a recap.

When I'm active on the mailing list, you can be sure that I'd complain if I didn't like it. ;-)

Show 6 quoted lines
>  * Tools renaming plan calls for removal of the backward
>    compatible command names (e.g. git-fsck-cache and
>    git-update-cache) sometime in the future.  This is scheduled
>    for 0.99.8 around beginning of October.  If somebody wants
>    extended amnesty period, this can be pushed back but unless I
>    hear otherwise...

I think the start of October is fine for Cogito. Cogito users usually upgrade both Cogito and GIT at once, it seems.

Show 8 quoted lines
>  * After reviewing the current set of commands, the following do
>    not seem to be useful anymore; Linus said he feels they can
>    go, and nobody else objected:
> 
>    git-diff-helper git-diff-stages git-export git-rev-tree
> 
>    I'd like to remove them before 1.0, and planning to do it
>    within the 0.99.8 timeframe unless I hear otherwise.
Cogito does not use any of those.
Show 8 quoted lines
>  * After Brian Gerst posted a patch to show 'modified' files in
>    ls-files [*2*], there was a brief discussion to change the
>    tagged output markings to make them more readable, but
>    neither Cogito nor StGIT seems to use tagged output.  I am
>    currently thinking about removing '-t' altogether.
> 
>    Again, unless I hear otherwise, I'd like to remove it within
>    the 0.99.8 timeframe.

Well, if it should be kept, it should certainly be in sync with git-diff-* tag letters. But Cogito uses only the diff tag letters and I'm not sure if tag letters for all files in repository would really be useful for anything.

Show 5 quoted lines
> [Footnote]
> 
> *1* Well, Pasky indicated he does not like some of the terms in
> the glossary in his recent Cogito release announcement, but that
> was unfortunately after the fact.

Yes. I would complain loudly during the discussion, but I unwisely skipped it at first and then didn't read the list for a few weeks. My fault, I have to make the best way out of the terminology mess I'm in now.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
Previous: Petr BaudisNext: Petr Baudis
Message 9 of 12 in “GIT - breaking backward compatibility”
  1. Junio C HamanoSep 20, 2005
  2. Brian GerstSep 20, 2005
  3. Linus TorvaldsSep 20, 2005
  4. Brian GerstSep 20, 2005
  5. Linus TorvaldsSep 20, 2005
  6. Petr BaudisSep 20, 2005
  7. Junio C HamanoSep 20, 2005
  8. Petr BaudisSep 20, 2005
  9. Petr BaudisSep 20, 2005
  10. Petr BaudisSep 22, 2005
  11. Junio C HamanoSep 23, 2005
  12. Sven VerdoolaegeSep 20, 2005

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.