Files
2012-02-21 01:15:00 -05:00

1 line
1.9 KiB
JSON

[{"user_id": 5778, "stars": [], "topic_id": 8134, "date_created": 1298403794.6307991, "message": "is it possible for me to use git-svn to determine the last SVN revision number that was pulled down?", "group_id": 106, "id": 181904}, {"user_id": 5778, "stars": [], "topic_id": 8134, "date_created": 1298403878.821666, "message": "any thoughts?", "group_id": 106, "id": 181926}, {"user_id": 5778, "stars": [], "topic_id": 8134, "date_created": 1298403777.2682869, "message": "We officially use SVN for our work repository, but I've been using git-svn for quite some time to interact with SVN.", "group_id": 106, "id": 181903}, {"user_id": 5778, "stars": [], "topic_id": 8134, "date_created": 1298403876.9244649, "message": "I'd like to resurrect a little script that pops up a notification when my local copy is out of date by comparing my \"working copy\" revision with the latest revision on the SVN server.", "group_id": 106, "id": 181923}, {"user_id": 1736, "stars": [{"date_created": 1298431382.2761431, "user_id": 5778}], "topic_id": 8134, "date_created": 1298405453.121413, "message": "git-svn sets up a remote head in the same way as a normal remote. You should be able to use the log on the commit that points to to find the rev.", "group_id": 106, "id": 182159}, {"user_id": 4631, "stars": [], "topic_id": 8134, "date_created": 1298426635.7604239, "message": "you can also see the \"regular\" svn repo info by running 'git svn info'", "group_id": 106, "id": 185503}, {"user_id": 1736, "stars": [], "topic_id": 8134, "date_created": 1298426839.328011, "message": "@widox On some our imported repos with 10k+ commits, git svn info can take 5 to 7 minutes so I would avoid it in a script.", "group_id": 106, "id": 185510}, {"user_id": 5778, "stars": [], "topic_id": 8134, "date_created": 1298431413.3831351, "message": "@coderanger Thanks for this suggestion--the git log had the information I was after! My script does exactly what I want now.", "group_id": 106, "id": 185625}]