Hi Davide, 2014-11-19 17:28 GMT+01:00 Davide G. M. Salvetti <salve+ev...@linux.it>: >>>>>> MG == Mosè Giordano [2014-11-19] > > MG> 2014-11-19 7:13 GMT+01:00 Davide G. M. Salvetti <salve+ev...@linux.it>: > > [...] > >>> I suggest to create a separated branch with this patch. You could >>> then rebase the branch as needed, as long as it's clearly documented >>> what the branch is for and that it will be rebased. > > MG> That's a good idea, but where do you mean it should be documented? > MG> AUCTeX page on Savannah? > > That would be a good place, i.e., > <http://www.gnu.org/software/auctex/development.html>. Also perhaps a > most natural place would be README.GIT? > > I would document there what every branch is for, as well as what's every > branch rebase policy, so people clearly know what to expect and what > branch should they base their work on, and don't get baffled by > unexpected rebase uses. We could just prepend such a description to the > current README.GIT content.
Done, thanks for the suggestion. Feel free the improve the descriptions of the branches. > BTW, while > we are at it, simplify-TeX-parse-error looks like a feature branch to > me, and I personally find that continuous merges with master hide the > progress on that branch: I would prefer to see it regularly rebased onto > master, rather than merged, as the history (as in git log) would be IMO > easier to follow; master could then be finally merged with > simplify-TeX-parse-error when that feature gets ready. Agreed, Tassilo, what do you think? Actually, I'd like to see this feature merged into master at some point. The last time I tested it, the new TeX-parse-TeX was able to catch some more errors (and some less) than the old one. `TeX-file-line-error' is great, but ideally AUCTeX should be able to catch all errors by itself. Bye, Mosè _______________________________________________ auctex-devel mailing list auctex-devel@gnu.org https://lists.gnu.org/mailman/listinfo/auctex-devel
