From: Brian Gerst <bgerst@didntduck.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: GIT - breaking backward compatibility
Date: Tue, 20 Sep 2005 00:12:35 -0400 [thread overview]
Message-ID: <432F8C33.5080603@didntduck.org> (raw)
In-Reply-To: <7vpsr4cx0f.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> 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.
>
> * 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...
>
> * 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.
>
> * 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.
>
>
> BTW, independent from any of these I'll be doing a 0.99.7a
> soonish for "fixes only" on top of 0.99.7.
>
>
> [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.
>
> *2* I haven't taken this patch not because I do not think
> showing 'modified' file is a bad idea but because showing cache
> dirty files as 'modified' did not feel right to me. I think
> doing what 'git-update-index --refresh' does without actually
> refreshing the cache status bits would be the right way to go.
Essentially what I want to do is:
git-ls-files --others | xargs git-update-index --add --
git-ls-files --deleted | xargs git-update-index --remove --
git-ls-files --modified | xargs git-update-index --
This will completely resync the index and cache to the working tree
state after applying a patch. git-update-index --refresh only updates
the stat info in the index. It does _not_ write a new cache object if
the file contents have actually changed.
Cogito would benefit from this too. It currently uses git-diff-index
and some ugly sed expressions in cg-commit to detect modified files.
If your objection is to calling the files modifed, then call it dirty or
something else.
--
Brian Gerst
next prev parent reply other threads:[~2005-09-20 4:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 2:07 GIT - breaking backward compatibility Junio C Hamano
2005-09-20 4:12 ` Brian Gerst [this message]
2005-09-20 4:33 ` Linus Torvalds
2005-09-20 4:41 ` Brian Gerst
2005-09-20 5:03 ` Linus Torvalds
2005-09-20 7:29 ` Petr Baudis
2005-09-20 6:19 ` Junio C Hamano
2005-09-20 13:08 ` Petr Baudis
[not found] ` <20050920062549.GI15165MdfPADPa@greensroom.kotnet.org>
[not found] ` <7v3bo06xv4.fsf@assigned-by-dhcp.cox.net>
2005-09-20 7:11 ` Sven Verdoolaege
2005-09-20 13:23 ` Petr Baudis
2005-09-22 14:41 ` Petr Baudis
2005-09-23 6:02 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=432F8C33.5080603@didntduck.org \
--to=bgerst@didntduck.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.