[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [AUCTeX-devel] [PATCH v3]: Merge /preview/ into top-level

From: Davide G. M. Salvetti
Subject: Re: [AUCTeX-devel] [PATCH v3]: Merge /preview/ into top-level
Date: Wed, 19 Nov 2014 17:28:50 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux)

>>>>>  MG == Mosè Giordano [2014-11-19]

MG> 2014-11-19 7:13 GMT+01:00 Davide G. M. Salvetti <address@hidden>:


>> 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.,
<>.  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.

Currently we just have two branches, i.e., master and
simplify-TeX-parse-error, but we might someday want to adopt a classic
maint, master, next plus feature-branches workflow (see
gitworkflows(7)); or some other model, as the need might be.  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.

Finally, Savannah uses cgit to display git repositories, and while I'm
not an expert, I see that cgitrc(5) lists `repo.readme' as an
interesting per repository configurable item to link a file (or a
refspec, which could `be master:README.git' in our case) to the about
repository page, which currently quite uninterestingly reads `foo' (see
<>; note that the same
`foo' also holds for a lot (all?) of the other Savannah git repositories
as well).  I think this needs a request to Savannah admins, which could
then add a local cgitrc to AUCTeX's git repository.  Also there is
`root-readme' which however is a global cgit option, and therefore
should be used accordingly to Savannah's cgit global configuration,
which I do now know.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]