Hi,
The git commit message section of our git guide has more content now:
http://wiki.eclipse.org/Linux_Tools_Project/Git#Commit_messages
Please follow the guidelines as best as you can. They're from here:
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
Andrew
I have been thinking about this for a while, but was prompted by
Andrew's email [1] to send a message to the list.
Changelogs are pain to deal with, they don't automerge, and the
authorship information is redundant.
On the other hand I find them useful in two ways: they force me to go
over
See https://hudson.eclipse.org/hudson/job/linuxtools-master/483/changes
Changes:
[Anithra P Janakiraman] Change feature version to 1.2.0
--
[...truncated 8677 lines...]
[INFO] Linux Tools Newlib Libhover Plug-in ... SUCCESS [0.793s]
[INFO]
See https://hudson.eclipse.org/hudson/job/linuxtools-master/484/changes
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
On 21:56:09 Friday 19 August 2011 Andrew Overholt wrote:
[Anithra P Janakiraman] Change feature version to 1.2.0
It looks like Anithra forgot to change the version in the matching
pom.xml. Where possible, please run local builds before pushing changes
so that we don't have broken builds.
* Alexander Kurtakov akurt...@redhat.com [2011-08-19 14:57]:
mvn tycho-versions:set-version -DnewVersion=YOUR_VERSION will do the right
thing keeping things in sync.
This seems promising but how should it be used? If I try it in the
top-level directory or in one of the project directories, I
On 22:19:57 Friday 19 August 2011 Andrew Overholt wrote:
* Alexander Kurtakov akurt...@redhat.com [2011-08-19 14:57]:
mvn tycho-versions:set-version -DnewVersion=YOUR_VERSION will do the
right thing keeping things in sync.
This seems promising but how should it be used? If I try it in the
* Alexander Kurtakov akurt...@redhat.com [2011-08-19 15:22]:
On 22:19:57 Friday 19 August 2011 Andrew Overholt wrote:
* Alexander Kurtakov akurt...@redhat.com [2011-08-19 14:57]:
mvn tycho-versions:set-version -DnewVersion=YOUR_VERSION will do the
right thing keeping things in sync.
On 23:01:13 Friday 19 August 2011 Andrew Overholt wrote:
* Alexander Kurtakov akurt...@redhat.com [2011-08-19 15:22]:
On 22:19:57 Friday 19 August 2011 Andrew Overholt wrote:
* Alexander Kurtakov akurt...@redhat.com [2011-08-19 14:57]:
mvn tycho-versions:set-version
mvn tycho-versions:set-version -DnewVersion=YOUR_VERSION will do the
Please note that if you run it in valgrind directory it will change the
valgrind parent pom and all references to it but it will not change the
versions of the bundles and features.
Ah. But if we want the source
On 23:29:56 Friday 19 August 2011 Andrew Overholt wrote:
mvn tycho-versions:set-version -DnewVersion=YOUR_VERSION will do
the
Please note that if you run it in valgrind directory it will change the
valgrind parent pom and all references to it but it will not change the
* Alexander Kurtakov akurt...@redhat.com [2011-08-19 16:31]:
On 23:29:56 Friday 19 August 2011 Andrew Overholt wrote:
mvn tycho-versions:set-version -DnewVersion=YOUR_VERSION will do
the
Please note that if you run it in valgrind directory it will change the
valgrind
On 23:37:40 Friday 19 August 2011 Andrew Overholt wrote:
* Alexander Kurtakov akurt...@redhat.com [2011-08-19 16:31]:
On 23:29:56 Friday 19 August 2011 Andrew Overholt wrote:
mvn tycho-versions:set-version -DnewVersion=YOUR_VERSION will
do the
Please note that if you
13 matches
Mail list logo
