Re: [PATCH v2] Add -ftabstop=WIDTH

["Christopher Li" <sparse@chrisli.org>]

On Sat, Jan 3, 2009 at 4:01 AM, Junio C Hamano <junio@pobox.com> wrote:
> "Hannes Eder" <hannes@hanneseder.net> writes:
>
>> diff --git a/lib.c b/lib.c
>> index 059ba3b..221e7b8 100644
>> --- a/lib.c
>> +++ b/lib.c
>> @@ -15,6 +15,8 @@
>>  #include <string.h>
>>  #include <unistd.h>
>>  #include <assert.h>
>> +#include <limits.h>
>> +#include <errno.h>
>
> These includes after Chris's simplification should not be needed, no?

Good catch. I incorporate it as well.

While you are here. I have a question regarding how to publish patch series
with git.

Take this patch as example. I want to have some repository to allow
others to pull the early version of the patch for testing. I also want
to incorporate
changes into the patch itself.

If I am using patch series. That is easy, just republish a new series.

With git, I can:
1) always submit incremental changes to master branch. Then the patch will
    be fragmented. I want the clean up version of the history.
2) Use rebase or cherry-pick to update the master branch. That will change
    the history of the commit. it causes trouble for people who pull the earlier
   version of the patch.
3) Always use a new branch to publish a new patch series. Then people who
   pull it need to know which branch to pull. It seems that I want an alias for
   the branch. On the client side it can use the same alias to pull different
   branch. I haven't figure out how to do that with git yet.

Any suggestions?

Thanks

Chris