This is the mail archive of the mailing list for the Archer project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Proposal to change branch maintenance

Tom> I don't propose renaming existing branches.

Jan> IMO if there should be a different naming the existing should be renamed,
Jan> otherwise it is more complicated/mess than it was.

It seems the consensus is to rename them.
So, let's do that.

Also I think we should delete all the branches that we got from
gdb.git.  There's no need for them in archer.git.

I'll do the branch deletions next week or so, then the renames after

Tom> Third, what about adopting a convention for a "README.archer" file in
Tom> the top-level of each branch?

Jan> That would not work for merges of multiple branches.  Some
Jan> ARCHER.branchname would work.

Ok, it turns out that --edit-description doesn't really do what we'd
like.  Bummer.

I found this that shows a way that we could make README.archer work
without excessive merge issues:

Alternatively we could pick the README file name based on the branch
name.  This isn't as convenient but it would also work.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]