Hello,
In my understanding, the ratio between the mere consumers of git on Windows vs.
people who compile git for Windows is 100,000 : 1. If there is a breaking
change in the workflow of the latter set, who use Visual Studio to build git
from source, I assume that is doable given a good reason
On Sun, Jul 26, 2015 at 11:28 AM, Eric Sunshine wrote:
> On Sun, Jul 26, 2015 at 12:36 AM, Karthik Nayak wrote:
>> On Sun, Jul 26, 2015 at 9:38 AM, Eric Sunshine
>> wrote:
>>> Also, it is helpful to reviewers if you include an interdiff at the
>>> bottom of your cover letter showing the changes
On Sun, Jul 26, 2015 at 12:36 AM, Karthik Nayak wrote:
> On Sun, Jul 26, 2015 at 9:38 AM, Eric Sunshine
> wrote:
>> Also, it is helpful to reviewers if you include an interdiff at the
>> bottom of your cover letter showing the changes from one version to
>> another. You can generate an interdiff
On Sun, Jul 26, 2015 at 9:42 AM, Eric Sunshine wrote:
>
> Should 'color' should be declared 'char *' rather than 'const char *'?
> It's always assigned via xstrdup(), and if declared 'char *', you
> wouldn't have to cast away the 'const' when freeing it.
>
yes, will change.
>
> While reviewing p
On Sun, Jul 26, 2015 at 01:03:59PM +0800, Paul Tan wrote:
> > Ideally the code would just be ordered as:
> >
> > - load config from git-config
> >
> > - override that with defaults inherited from a previous run
> >
> > - override that with command-line parsing
>
> So I'm more in favor of th
On Sun, Jul 26, 2015 at 10:16 AM, Eric Sunshine wrote:
> On Fri, Jul 24, 2015 at 3:04 PM, Karthik Nayak wrote:
>> From: Karthik Nayak
>>
>> In 'tag.c' we can print N lines from the annotation of the tag using
>> the '-n' option. Copy code from 'tag.c' to 'ref-filter' and
>> modify 'ref-filter' t
On Fri, Jul 24, 2015 at 3:04 PM, Karthik Nayak wrote:
> Since 'ref-filter' only has an option to match path names add an
> option for plain fnmatch pattern-matching.
>
> This is to support the pattern matching options which are used in `git
> tag -l` and `git branch -l` where we can match patterns
On Sun, Jul 26, 2015 at 4:10 AM, Junio C Hamano wrote:
> Karthik Nayak writes:
>
>> @@ -1180,19 +1181,17 @@ static int cmp_ref_sorting(struct ref_sorting *s,
>> struct ref_array_item *a, stru
>>
>> get_ref_atom_value(&state, a, s->atom, &va);
>> get_ref_atom_value(&state, b, s->atom,
On Sat, Jul 25, 2015 at 2:09 AM, Jeff King wrote:
> Yeah, I think this hunk is to blame (though I just read the code and did not
> test):
>
> @@ -658,6 +665,8 @@ fi
> if test "$(cat "$dotest/threeway")" = t
> then
> threeway=t
> +else
> + threeway=f
> fi
>
> It comes after the com
On Fri, Jul 24, 2015 at 3:04 PM, Karthik Nayak wrote:
> From: Karthik Nayak
>
> In 'tag.c' we can print N lines from the annotation of the tag using
> the '-n' option. Copy code from 'tag.c' to 'ref-filter' and
> modify 'ref-filter' to support printing of N lines from the annotation
> of tags.
>
On Sun, Jul 26, 2015 at 9:38 AM, Eric Sunshine wrote:
> On Fri, Jul 24, 2015 at 3:04 PM, Karthik Nayak wrote:
>> Add a new atom "align" and support %(align:X) where X is a number.
>> This will align the preceeding atom value to the left followed by
>
> Do you mean "succeeding" or "following" or "
On Sat, Jul 25, 2015 at 12:15 AM, Karthik Nayak wrote:
> On Sat, Jul 25, 2015 at 3:16 AM, Junio C Hamano wrote:
>> Karthik Nayak writes:
>>> Make color which was considered as an atom, to use
>>> ref_formatting_state and act as a pseudo atom. This allows
>>> interchangeability between 'align' an
On Fri, Jul 24, 2015 at 3:04 PM, Karthik Nayak wrote:
> Make color which was considered as an atom, to use
> ref_formatting_state and act as a pseudo atom. This allows
> interchangeability between 'align' and 'color'.
>
> Signed-off-by: Karthik Nayak
> ---
> diff --git a/ref-filter.c b/ref-filter
On Fri, Jul 24, 2015 at 3:04 PM, Karthik Nayak wrote:
> Add a new atom "align" and support %(align:X) where X is a number.
> This will align the preceeding atom value to the left followed by
Do you mean "succeeding" or "following" or "next" (or something)
rather than "preceding"?
> spaces for a
I'm trying to clean up the commit history of a git repository by
removing
certain files. The repository contains signed commits, and when I try
to use
git filter-branch, the PGP signature is converted to the first line
of the
commit message.
It should be possible to craft a filter that remove
On Sat, Jul 25, 2015 at 1:17 PM, Adam Liter wrote:
> Hello,
>
> I'm trying to clean up the commit history of a git repository by removing
> certain files. The repository contains signed commits, and when I try to use
> git filter-branch, the PGP signature is converted to the first line of the
> co
On Sat, Jul 25, 2015 at 10:41 AM, Junio C Hamano wrote:
> Jeff King writes:
>
>> On Fri, Jul 24, 2015 at 08:07:49AM -0700, Junio C Hamano wrote:
>>
>>> Yeah, you actually convinced me reasonably well that it would
>>> happen. I'd never use it myself. If people want to shoot
>>> themselves in th
Karthik Nayak writes:
> @@ -1180,19 +1181,17 @@ static int cmp_ref_sorting(struct ref_sorting *s,
> struct ref_array_item *a, stru
>
> get_ref_atom_value(&state, a, s->atom, &va);
> get_ref_atom_value(&state, b, s->atom, &vb);
> - switch (cmp_type) {
> - case FIELD_STR:
> +
Dear Professor
You can upload now your invited paper for our conference in Malta, August
17-19: www. wseas. org until July 27, 2015
OR
for our conference in Seoul, South Korea, September 5-7, 2015
until August 20, 2015. URL www. wseas. org
Invited Speakers will have also publication in one of o
Hello,
I'm trying to clean up the commit history of a git repository by
removing certain files. The repository contains signed commits, and when
I try to use git filter-branch, the PGP signature is converted to the
first line of the commit message.
Is this the expected behavior? If so, is th
Hi Bing,
I don't think the approach you're outlining in your most recent e-mail
is going to work particularly well for you. See my replies in-line.
I have devised a solution that should work much better for you, it's a
tiny bash script and a set of naming conventions for repository
branches. I've
Jeff King writes:
> On Fri, Jul 24, 2015 at 08:07:49AM -0700, Junio C Hamano wrote:
>
>> Yeah, you actually convinced me reasonably well that it would
>> happen. I'd never use it myself. If people want to shoot
>> themselves in the foot, be my guest ;-)
>>
>> Perhaps we should drop this, and g
Jeff King writes:
> This works for "format-patch -s". But I guess that leaves open the
> question of "commit --signoff". It should not matter when making a
> commit new (after all, you have not yet had a chance to put the "---"
> in). But something like "git commit --amend --signoff" might want t
23 matches
Mail list logo
