On Tue, Sep 01, 2015 at 02:27:22AM -0400, Jason Merrill wrote:
> On 08/29/2015 10:58 AM, Dominique d'Humières wrote:
> >>For Jakub or anyone else wanting a key to associate a file with a commit,
> >>they can decide for themselves
> >>what date format they want to use and whether to bother with the
On 09/01/2015 11:59 AM, Eric S. Raymond wrote:
Jason Merrill :
Here's an improved version:
You wrote:
# git scommit - list most recent commit that matches
.
# Must also specify a branch to search or --all.
Where must the branch argument appear with respect to the other arguments?
After
Jason Merrill :
> Here's an improved version:
You wrote:
# git scommit - list most recent commit that matches
.
# Must also specify a branch to search or --all.
Where must the branch argument appear with respect to the other arguments?
Am I correct that this should be applied by creating or
On 09/01/2015 05:21 AM, Eric S. Raymond wrote:
Jason Merrill :
Given git aliases:
stamp = show -s --format='%cI!%ce'
scommit = "!f(){ d=${1%%!*}; a=${1##*!}; arg=\"--until=$d -1\"; if [ $a != $1 ]; then
arg=\"$arg --committer=$a\"; fi; shift; git rev-list $arg ${1:+\"$@\"}; };
On 1 September 2015 at 10:21, Eric S. Raymond wrote:
> Jason Merrill :
>> Given git aliases:
>>
>> >stamp = show -s --format='%cI!%ce'
>> >scommit = "!f(){ d=${1%%!*}; a=${1##*!}; arg=\"--until=$d -1\"; if
>> > [ $a != $1 ]; then arg=\"$arg --committer=$a\"; fi; shift; git rev-list
Jason Merrill :
> Given git aliases:
>
> >stamp = show -s --format='%cI!%ce'
> >scommit = "!f(){ d=${1%%!*}; a=${1##*!}; arg=\"--until=$d -1\"; if [
> > $a != $1 ]; then arg=\"$arg --committer=$a\"; fi; shift; git rev-list $arg
> > ${1:+\"$@\"}; }; f"
> >smaster = "!f(){
On 08/29/2015 10:58 AM, Dominique d'Humières wrote:
For Jakub or anyone else wanting a key to associate a file with a commit, they
can decide for themselves
what date format they want to use and whether to bother with the user id. I
would think that if he is only
interested in commits on the tr
Jason Merrill :
> On 08/26/2015 01:11 PM, Eric S. Raymond wrote:
> >What I usually do with old commit references in comments is map them
> >to what I call an "action stamp" - a user ID followed by an RFC3339
> >date. While this is theoretically not quite adequate, in practice
> >collisions are rar
> For Jakub or anyone else wanting a key to associate a file with a commit,
> they can decide for themselves
> what date format they want to use and whether to bother with the user id. I
> would think that if he is only
> interested in commits on the trunk (and so should use log --first-parent),
On 08/26/2015 01:11 PM, Eric S. Raymond wrote:
What I usually do with old commit references in comments is map them
to what I call an "action stamp" - a user ID followed by an RFC3339
date. While this is theoretically not quite adequate, in practice
collisions are rare to nonexistent.
For gene
th old commit references in comments is map them
to what I call an "action stamp" - a user ID followed by an RFC3339
date. While this is theoretically not quite adequate, in practice
collisions are rare to nonexistent.
Action stamps have the major advantages that they are self-desc
11 matches
Mail list logo
