-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Write .gituprevision in the root of the clone #19
Comments
|
Hello, I just pushed out an update to create a .gituprevision file in the target path which stores the branch, a '-' and the first nine digits of the want commit. How does it look? |
|
Thank you for the quick turnaround, looking into. A hyphen might be problematic because a vendor branch can contain a hyphen. When |
|
Tested. Works for me. I would highly prefer something which is not allowed in a branch name. Colon seems good to me. |
|
I just changed the separator to a colon and pushed the changes. |
|
Works for me! Happily closing this issue. |
|
If you'd review, I'd be happy to next week. |
|
Sounds good, tag me on the review and I'll look. |
|
Here you go folks: freebsd/freebsd-src#449 |
Since I moved from Subversion to gitup I do not see revision in
uname -aanymore. This is especially problematic for users which have to report issues and requested the used commit id. I know that this is not really related to gitup, but here is my proposal:When a clone or a pull happens to a section create/update a
.gituprevisionfile in that same target directory ideally to the same format the official Git client would procude. In the next stepsys/conf/newvers.shcan be modified to readin that file and makeuname -ajust like using Subversion or Git.Git code: https://github.com/freebsd/freebsd-src/blob/098dbd7ff7f3da9dda03802cdb2d8755f816eada/sys/conf/newvers.sh#L249-L264
The text was updated successfully, but these errors were encountered: