Thanks for reviewing Mirko, see below.
2015-05-02 23:45 GMT+02:00 Mirko Friedenhagen :
> Hello Baptiste,
>
> first of all, thanks for your efforts, mind-boggling git-vodoo :-).
> One thing I noted (when inspecting the repository with SourceTree):
> * When I take a look at a repository which was g
Hello Baptiste,
you are right, there seem to be no real branches, so maybe it's just
the SourceTree visualisation of the tags which look like branches. Or
maybe it is because in line 107 you only push the master branch as far
as I understand it?
I just play around with "git push --all origin", se
Hi Mirko,
which version of Git do you use?
i can do a git tag and get the following output:
$ git tag
extra-enforcer-rules-1.0-alpha-1
extra-enforcer-rules-1.0-alpha-2
extra-enforcer-rules-1.0-alpha-3
extra-enforcer-rules-1.0-alpha-4
extra-enforcer-rules-1.0-alpha-5
extra-enforcer-rules-1.0-bet
Hi all,
I'd like to release version 2.1 of the JAXB2 Maven Plugin, which is a major
plugin
upgrade that contains rewritten plugin mechanics, updates to the JAXB2
toolset
and several bug fixes. The 2.x versions of the plugin are not backwards
compatible with the 1.x versions.
The JAXB2-Maven-Plugi
In that situation you should use gitk --tags because the corresponding
commits are actually not part of the master branch. As indeed they will be
in the future.
Actually, gitk only shows the history of the current branch. So in general
when you want to see everything, either use gitk -all or gitk
Hello,
first of all thanks for the hints how to use these tools. I just find it
unfortunate that you have to use specific options to standard tooling to
see a meaningful history where I may easily see the tags.
Regards
Mirko
--
Sent from my mobile
On May 3, 2015 11:58 AM, "Baptiste Mathus" wrot
Hi,
As the deadline is coming close, and the migration script seems to work,
I'd like to *propose we ask Codehaus support to put our svn in readonly
mode and provide us with an up-to-date dump.*
I'm gonna start a dedicated vote for it to make sure everyone sees it.
2015-05-03 13:44 GMT+02:00 Mir
Hi all,
As a followup to previous threads, I guess it's time for us to try and move
on.
Indeed, the announcement says services should be shut down the 17 May.
So, to go forward, I'd like to ask Codehaus support to put the SVN in RO
mode.
This vote will be open for 72h and will NOT succeed by laz
+1 from my side, the earlier the better.
Regards
Mirko
--
Sent from my mobile
On May 3, 2015 9:49 PM, "Baptiste Mathus" wrote:
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and
> move on.
> Indeed, the announcement says services should be shut down the 17 May.
+1
2015-05-03 21:48 GMT+02:00 Baptiste Mathus :
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and
> move on.
> Indeed, the announcement says services should be shut down the 17 May.
>
> So, to go forward, I'd like to ask Codehaus support to put the SVN in RO
> m
+1.
I am looking forward to the Git era. :)
2015-05-03 21:48 GMT+02:00 Baptiste Mathus :
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and
> move on.
> Indeed, the announcement says services should be shut down the 17 May.
>
> So, to go forward, I'd like to as
+1
Big thanks for doing this ...
-Dan
On Sun, May 3, 2015 at 12:52 PM, David Karlsen
wrote:
> +1
>
> 2015-05-03 21:48 GMT+02:00 Baptiste Mathus :
>
>> Hi all,
>>
>> As a followup to previous threads, I guess it's time for us to try and
>> move on.
>> Indeed, the announcement says services shou
Hi Baptiste,
+1 from me...
Kind regards
Karl Heinz Marbaise
On 5/3/15 9:48 PM, Baptiste Mathus wrote:
Hi all,
As a followup to previous threads, I guess it's time for us to try and
move on.
Indeed, the announcement says services should be shut down the 17 May.
So, to go forward, I'd like to
+1
/Anders (mobile)
Den 3 maj 2015 21:49 skrev "Baptiste Mathus" :
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and
> move on.
> Indeed, the announcement says services should be shut down the 17 May.
>
> So, to go forward, I'd like to ask Codehaus support to pu
There is no release in progress it seems, thus+1
let's go.
On Sun, May 3, 2015 at 9:41 PM, Baptiste Mathus wrote:
> Hi,
>
> As the deadline is coming close, and the migration script seems to work,
> I'd like to *propose we ask Codehaus support to put our svn in readonly
> mode and provide us wi
+1
On Sun, May 3, 2015 at 9:48 PM, Baptiste Mathus wrote:
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and
> move on.
> Indeed, the announcement says services should be shut down the 17 May.
>
> So, to go forward, I'd like to ask Codehaus support to put the SV
+1
On Sun, May 3, 2015 at 11:00 PM, Arnaud Héritier
wrote:
> +1
>
> On Sun, May 3, 2015 at 9:48 PM, Baptiste Mathus
> wrote:
>
>> Hi all,
>>
>> As a followup to previous threads, I guess it's time for us to try and
>> move on.
>> Indeed, the announcement says services should be shut down the 17
On Sun, 3 May 2015 21:48:41 +0200
Baptiste Mathus wrote:
Let'ss go!
:)
+1
Good work Batman.
tony.
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and move
> on.
> Indeed, the announcement says services should be shut down the 17 May.
>
> So, to go forw
+1
On 4 May 2015 at 05:48, Baptiste Mathus wrote:
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and
> move on.
> Indeed, the announcement says services should be shut down the 17 May.
>
> So, to go forward, I'd like to ask Codehaus support to put the SVN in RO
+1
Milos
On Mon, May 4, 2015 at 5:48 AM, Baptiste Mathus wrote:
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and
> move on.
> Indeed, the announcement says services should be shut down the 17 May.
>
> So, to go forward, I'd like to ask Codehaus support to put
> There is no release in progress it seems, thus+1
> let's go.
>
There is a release of the jaxb2 mojo in progress.
/Anders
>
>
> On Sun, May 3, 2015 at 9:41 PM, Baptiste Mathus
> wrote:
>
>> Hi,
>>
>> As the deadline is coming close, and the migration script seems to work,
>> I'd like to *prop
21 matches
Mail list logo
