On Mon, Jul 27, 2015 at 5:18 PM, Duy Nguyen wrote:
> On Mon, Jul 27, 2015 at 2:39 PM, Jacob Keller wrote:
>> On Sun, Jul 26, 2015 at 5:39 PM, Duy Nguyen wrote:
>>> On Sun, Jul 26, 2015 at 11:08 AM, Eric Sunshine
>>> wrote:
You can generate an interdiff with "git diff branchname-v4
br
Karthik Nayak writes:
> I've been working on the same branch, and that's why I didn't really
> provide interdiff's,
You can keep working on the same branch and tag versions you send to the
list. "This state is what I sent to the list as vX" is something that does not
change in time hence a tag a
On Mon, Jul 27, 2015 at 2:39 PM, Jacob Keller wrote:
> On Sun, Jul 26, 2015 at 5:39 PM, Duy Nguyen wrote:
>> On Sun, Jul 26, 2015 at 11:08 AM, Eric Sunshine
>> wrote:
>>> You can generate an interdiff with "git diff branchname-v4
>>> branchname-v5", for instance.
>>
>> Off topic. But what stops
On Sun, Jul 26, 2015 at 5:39 PM, Duy Nguyen wrote:
> On Sun, Jul 26, 2015 at 11:08 AM, Eric Sunshine
> wrote:
>> You can generate an interdiff with "git diff branchname-v4
>> branchname-v5", for instance.
>
> Off topic. But what stops me from doing this often is it creates a big
> mess in "git t
On Sun, Jul 26, 2015 at 11:08 AM, Eric Sunshine wrote:
> You can generate an interdiff with "git diff branchname-v4
> branchname-v5", for instance.
Off topic. But what stops me from doing this often is it creates a big
mess in "git tag -l". Do we have an option to hide away some
"insignificant:"
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: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 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
On Sat, Jul 25, 2015 at 4:30 AM, Junio C Hamano wrote:
> Junio C Hamano writes:
>
>> Karthik Nayak writes:
>>
>>> -if (!ref->value) {
>>> -populate_value(ref);
>>> +/*
>>> + * If the atom is a pseudo_atom then we re-populate the value
>>> + * into the ref_formatting_s
Junio C Hamano writes:
> Karthik Nayak writes:
>
>> -if (!ref->value) {
>> -populate_value(ref);
>> +/*
>> + * If the atom is a pseudo_atom then we re-populate the value
>> + * into the ref_formatting_state stucture.
>> + */
>> +if (!ref->value || ref->value[a
Karthik Nayak writes:
> - if (!ref->value) {
> - populate_value(ref);
> + /*
> + * If the atom is a pseudo_atom then we re-populate the value
> + * into the ref_formatting_state stucture.
> + */
> + if (!ref->value || ref->value[atom].pseudo_atom) {
> +
From: Karthik Nayak
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
spaces for a total length of X characters. If X is less than the item
size, the entire atom value is printed.
Helped-by: Duy Nguyen
Helped-by:
13 matches
Mail list logo
