IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Only use the bzr and git information when there's
a .bzr or .git in the top branch directory
I use bzr for my home directory and
bzr version-info in ~/devel/samba/4.0/samba4-git
gives the info about the ~/.bzr branch
metze
(This used to be commit e4df2e1c2d302613b1e7f44f13db9435bdafb30f)
The plan is to actually synchronize with SAMBA_4_0's mkversion.sh,
which is more elaborate. But there are a few differences in
behaviour I still have to check. So I am cheching this here in for
a start...
Michael
(This used to be commit dec7e31f298c565b49b7bd650e164274d0f61778)
We need the option to add an 'a' if we're already in pre or rc state
with the next release.
Bugzilla Bug 2618
(This used to be commit 26bf1d223efd011ca7c4d5c7d5de23d0f9ad0823)
display the SVN revision in svk build of tree's directly mirrored from samba.org
metze
(This used to be commit 110c0f6f36b8a5e7b0e1bf4477605ed81aca5580)
use 'Last Change Rev:' instead of 'Revision:' from the svn info output
for setting the SVN_REVISION in version.h
metze
(This used to be commit 7cc35ba06644669e64460b03c141a23ad7a516d7)
as we decide to not do 3.0.2a releases anymore,
remove the generation stuff from VERSION and mkversion.sh
metze
(This used to be commit 25cbca89baa89327384e80ad5f71577c3db6d6a2)