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Ƃ

Reply via email to