commit

I want to get a list of the latest commits on a certain remote Git repository. However, I do not want to create a clone because that takes too long. With SVN, I can simply pass along a username and password. With Git I haven't found an option to do this. Also, is there an XML output option like with SVN? This is probably not exactly what you want, but you could create a shallow clone using the --depth option to git clone . That clones only the last n revisions. It still copies all the content, though. For XML-like formatting you could use a custom log format like this: git log --pretty=format:

I have two branches A and B in a project that I am working on. B differs from A by a single commit, which is a section of the code completely independent from what I'm working on for the next while (aka, I will have many commits I want to push to both branch A and B). Is there any way in git that I can commit to both branch A and branch B at the same time, without having to commit it to one branch, checkout the other, and try to cherry pick out the commit(s). You could: make all your commits on A rebase B on top of A (if you haven't pushed B already, that is) That way, B will include all

I'm currently working with Apache and SVN with ActiveDirectory Authentication. The user is using TortoiseSVN client. I should point out that I have 2 repos with same name and different mapping but redirected to the same "user url" since the permissions are the same for both repos. eg 'http://mysrvr/svn/foo/bar/corge' and 'http://mysrvr/svn/foo/corge' or 'http://mysrvr/svn/foo/bar/corge and' 'http://mysrvr/svn/foo/grault/corge' This 2 repos thing is replicated with 8 "repo pairs" and the remaining 7 are working just fine. Here is my error: Commit failed(details follow): access to '/svn/myDir

Per accident I committed twice because I forgot to add two files. Can I remove a specific commit from the log? I want to delete commit № 4. The simple answer is "no", because Subversion doesn't know how to resolve the case when you add a commit, someone else updates their checkout, and then you remove the commit from history. There might or might not be a complex answer involving surgery on the Subversion storage. Lazy Badger AFAICS, you have not delete r4, but merge with r5, yes? In general, SVN commit history is immutable, as Sii said - and if you haven't rights delete/create repo - you can