Le 14/01/2020 à 17:07, Peter Bergner a écrit :
As somewhat of a git newbie and given gcc developers will do a git push of
our changes rather than employing a git pull development model, I'd like
a little hand holding on what my new gcc git workflow should be, so I don't
screw up the upstream repo
Le 11/01/2020 à 14:49, Jakub Jelinek a écrit :
On Sat, Jan 11, 2020 at 07:43:17AM -0600, Segher Boessenkool wrote:
On Fri, Jan 10, 2020 at 07:50:02PM +0100, Jakub Jelinek wrote:
Maybe even add https://gcc.gnu.org/gNNN for 7-40 hexadecimal digits
redirect to https://gcc.gnu.org/git/gitweb.cg
Le 30/12/2019 à 01:18, Joseph Myers a écrit :
Do "git log egcs_1_1_2_prerelease_2" in gcc-reparent, for example. The
history ends up containing two different versions of SVN r5 and of many
other commits.
When trying to migrate Blender from svn to git, we actually tried
git-svn first, and it
Le 29/12/2019 à 18:30, Ian Lance Taylor via gcc a écrit :
On Sun, Dec 29, 2019 at 5:49 AM Julien '_FrnchFrgg_' RIVAUD
wrote:
Which brings me to something I find strange in your policy: to me,
merges from trunk to branches should be rare if not nonexistent. And you
are deciding to banish merges
Le 28/12/2019 à 21:28, Segher Boessenkool a écrit :
On Sat, Dec 28, 2019 at 05:11:47PM +, Richard Earnshaw (lists) wrote >> I
disagree. The review comments will show up as additional commits on
the branch and can be tracked back to such events. Once history gets
flattened into a major sin
