Thanks for help ;)
It seems it was obvious, but I got completely misguided by "git
describe" - it should return the most recent tag name and I was (I am?)
confused why it returns the "beta1" one...
Michał
W dniu 07.05.2012 15:41, Jonathan Ellis pisze:
$ git tag
...
cassandra-1.0.9
cassandra-1.1.0
cassandra-1.1.0-beta1
cassandra-1.1.0-beta2
cassandra-1.1.0-rc1
...
$ git checkout cassandra-1.1.0
On Mon, May 7, 2012 at 8:28 AM, Michal Michalski<mich...@opera.com> wrote:
Hi,
Let's say I want to use Cassandra's Git repository to build my own Cassandra
.deb file which is _exactely_ the same as specified release (for example:
cassandra-1.1) and apply there some patches of my choice. Could you please
explain me how can I check which commit should I pick to do it properly?
I think that there's an easy way to check it, but - unluckily - I don't know
it (I'm not very familiar with git) or I miss something. I was expecting
something like a tag or so, but I can't find anything that will make me sure
that I found the commit I was looking for.
Of course I can check tags, but they don't look like they are up-to-date...
michal@aperture:~/workspace/cassandra-trunk$ git status
# On branch cassandra-1.1
(...)
michal@aperture:~/workspace/cassandra-trunk$ git describe
cassandra-1.1.0-beta1-529-g8b81c8f
(beta1?!)
I know I can check debian/changelog for the last "New Release" message and
then find/guess the appropriate commit basing on author, date/time and
commit message, but I don't think it's the best approach ;)
--
Kind regards,
Michał
