From: merlyn@stonehenge•com (Randal L. Schwartz)
To: esr@thyrsus•com
Cc: Jacob Helwig <jacob.helwig@gmail•com>,
Eric Raymond <esr@snark•thyrsus.com>,
git@vger•kernel.org
Subject: Re: Status of all files (was: Re: How can I tell if a file is ignored by git?
Date: Fri, 09 Apr 2010 05:11:12 -0700 [thread overview]
Message-ID: <864ojkx1un.fsf@red.stonehenge.com> (raw)
In-Reply-To: <20100409113248.GB27353@thyrsus.com> (Eric Raymond's message of "Fri, 9 Apr 2010 07:32:48 -0400")
>>>>> "Eric" == Eric Raymond <esr@thyrsus•com> writes:
Eric> There could be something better. Emacs VC mode, and other similar
Eric> front ends, would be greatly aided by a command that lists all files,
Eric> each with a status code it can understand. Our canonical list
Eric> (omitting two that apply only to locking systems) is:
A lot of these don't make sense for git and other DVCS. How have
hg and bzr interpreted these "canonical" states?
For example:
Eric> 'needs-update The file has not been edited by the user, but there is
Eric> a more recent version on the current branch stored
Eric> in the master file.
This makes sense only with a file-based VCS, not a tree-based VCS like
git.
Eric> 'needs-merge The file has been edited by the user, and there is also
Eric> a more recent version on the current branch stored in
Eric> the master file. This state can only occur if locking
Eric> is not used for the file.
Ditto.
Eric> 'removed Scheduled to be deleted from the repository
Eric> on next commit.
Not useful in git.
Eric> 'missing The file is not present in the file system, but the VC
Eric> system still tracks it.
Not available in git. (If it's not a real file, it can't be tracked. :)
Eric> 'ignored The file showed up in a dir-status listing with a flag
Eric> indicating the version-control system is ignoring it,
Eric> 'unregistered The file is not under version control.
These two would be identical in git.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge•com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
next prev parent reply other threads:[~2010-04-09 12:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 4:04 How can I tell if a file is ignored by git? Eric Raymond
2010-04-09 4:10 ` Jacob Helwig
2010-04-09 11:32 ` Status of all files (was: " Eric Raymond
2010-04-09 12:11 ` Randal L. Schwartz [this message]
2010-04-09 13:20 ` Eric Raymond
2010-04-10 19:07 ` Junio C Hamano
2010-04-09 12:56 ` Jakub Narebski
2010-04-09 14:02 ` Eric Raymond
2010-04-09 14:23 ` Matthieu Moy
2010-04-09 16:24 ` Eric Raymond
[not found] ` <z2h62a3a9cb1004091615q52bd5f5aqc24079de7f0038ba@mail.gmail.com>
2010-04-09 23:18 ` Daniel Grace
2010-04-10 3:35 ` Eric Raymond
2010-04-09 16:52 ` Junio C Hamano
2010-04-09 14:50 ` Jakub Narebski
2010-04-10 22:12 ` Status of all files Paolo Bonzini
2010-04-11 10:25 ` Jeff King
2010-04-09 4:50 ` How can I tell if a file is ignored by git? Ramkumar Ramachandra
2010-04-09 5:01 ` Ævar Arnfjörð Bjarmason
2010-04-09 10:50 ` Eric Raymond
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=864ojkx1un.fsf@red.stonehenge.com \
--to=merlyn@stonehenge$(echo .)com \
--cc=esr@snark$(echo .)thyrsus.com \
--cc=esr@thyrsus$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jacob.helwig@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox