[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [AUCTeX-devel] bidi patch
From: |
Uwe Brauer |
Subject: |
Re: [AUCTeX-devel] bidi patch |
Date: |
Sat, 17 Sep 2016 20:12:54 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
> 2016-09-17 19:15 GMT+02:00 Uwe Brauer <address@hidden>:
> The history of a repository is valuable, but flooding it with many
> oneliner changes makes it somewhat less useful. I sometimes do this
> with my personal and private projects, but if the code has to be seen
> by other people these microchanges are often more a nuisance for other
> readers as they add nothing to the history.
Ok, but how to you do this with your local repos? I mean
suppose you clone the auctex repo. And start a cool new feature in a
branch. Commit several times etc. then
- do you merge with master and send that patch (or push it)
- do you rebase and collapse.
- do it manually?
> That's different if you add oneliner fixes after the patch has been
> already installed into the repository, that little change cannot be
> avoided.
Uwe
- [AUCTeX-devel] bidi patch, Uwe Brauer, 2016/09/09
- Re: [AUCTeX-devel] bidi patch, Mosè Giordano, 2016/09/17
- Re: [AUCTeX-devel] bidi patch, Uwe Brauer, 2016/09/17
- Re: [AUCTeX-devel] bidi patch, Mosè Giordano, 2016/09/17
- Re: [AUCTeX-devel] bidi patch, Uwe Brauer, 2016/09/17
- Re: [AUCTeX-devel] bidi patch, Mosè Giordano, 2016/09/17
- Re: [AUCTeX-devel] bidi patch, Uwe Brauer, 2016/09/17
- Re: [AUCTeX-devel] bidi patch, Mosè Giordano, 2016/09/17
- Re: [AUCTeX-devel] bidi patch,
Uwe Brauer <=
- Re: [AUCTeX-devel] bidi patch, Tassilo Horn, 2016/09/18
- Re: [AUCTeX-devel] bidi patch, Uwe Brauer, 2016/09/18
- Re: [AUCTeX-devel] bidi patch, Tassilo Horn, 2016/09/18
- Re: [AUCTeX-devel] bidi patch, Uwe Brauer, 2016/09/18
- Re: [AUCTeX-devel] bidi patch, Uwe Brauer, 2016/09/18
- Re: [AUCTeX-devel] bidi patch, Mosè Giordano, 2016/09/18
Re: [AUCTeX-devel] bidi patch, Uwe Brauer, 2016/09/17