On Tue, 19 Nov 2019 at 23:52, Nicholas Krause wrote:
>
>
>
> On 11/19/19 6:44 PM, Joseph Myers wrote:
> > On Tue, 19 Nov 2019, Segher Boessenkool wrote:
> >
> >> Most of the time after I type "git log" I type "/\<123456\>". We need
> >> to keep a way to easily map SVN revision ids to git commits,
On Tue, 19 Nov 2019 at 23:29, Segher Boessenkool
wrote:
>
> On Tue, Nov 19, 2019 at 02:36:21PM -0500, Eric S. Raymond wrote:
> > Jason Merrill :
> > > Well, I was thinking of also giving some clue of what the commit was
> > > about. One possibly cut-off line accomplishes that, a simple revision
>
Hi,
After personal reflection on my current day-to-day involvement with the
GCC project and the expected behaviours and responsibilities delegated to
GNU project maintainers, I have come to the conclusion that the AArch64
port maintenance role is not one I am able to continue to commit to.
This
On 20/11/2019 09:31, James Greenhalgh wrote:
Hi,
After personal reflection on my current day-to-day involvement with the
GCC project and the expected behaviours and responsibilities delegated to
GNU project maintainers, I have come to the conclusion that the AArch64
port maintenance role is not
On Wed, Nov 20, 2019 at 08:58:05AM +, Jonathan Wakely wrote:
> > Most of the time after I type "git log" I type "/\<123456\>". We need
> > to keep a way to easily map SVN revision ids to git commits, and
>
> As a aside, I use these aliases often with the current git-svn repo:
>
> $ git help
On 20/11/2019 11:27, Segher Boessenkool wrote:
On Wed, Nov 20, 2019 at 08:58:05AM +, Jonathan Wakely wrote:
Most of the time after I type "git log" I type "/\<123456\>". We need
to keep a way to easily map SVN revision ids to git commits, and
As a aside, I use these aliases often with the
On Wed, Nov 20, 2019 at 11:30:36AM +, Richard Earnshaw (lists) wrote:
> On 20/11/2019 11:27, Segher Boessenkool wrote:
> >On Wed, Nov 20, 2019 at 08:58:05AM +, Jonathan Wakely wrote:
> >>These won't work once we move to Git though.
> >
> >It would be good if whatever convention we do for co
On Wed, Nov 20, 2019 at 6:27 AM Segher Boessenkool <
seg...@kernel.crashing.org> wrote:
> It would be good if whatever convention we do for commit messages and
> their first line would be machine parseable as well.
>
The first line should be useful to humans, machines can parse the whole
message.
Hi,
After a simple research on your company we realized that you are one of the
exhibitors at "The Trophex Show Expo 2020"
Would you be interested to acquire the list of 5,500 global industry
professionals' attendees who are going to attend The Trophex Show? If you
feel this might bring
On 19/11/2019 23:44, Joseph Myers wrote:
> I do think "Related to PR N (description)" or similar is a good
> summary line to insert where the present summary line is just a ChangeLog
> date/author line.
i agree.
Sorry for not responding sooner.
Thanks Martin.
Like Joel we have a third party solution to instrumentation. Part of
my objection to the third party solution is freedom. There are
customizations we would like, but not having source we're at the mercy
of the vendor both for whether it gets done
On Wed, Nov 20, 2019 at 09:25:19AM -0500, Jason Merrill wrote:
> On Wed, Nov 20, 2019 at 6:27 AM Segher Boessenkool <
> seg...@kernel.crashing.org> wrote:
>
> > It would be good if whatever convention we do for commit messages and
> > their first line would be machine parseable as well.
>
> The f
On 19/11/2019 23:44, Joseph Myers wrote:
> On Tue, 19 Nov 2019, Segher Boessenkool wrote:
>
>> Most of the time after I type "git log" I type "/\<123456\>". We need
>> to keep a way to easily map SVN revision ids to git commits, and
>> something a bit more elegant than the ugly git-svn footers wo
13 matches
Mail list logo
