[git-users] Re: Cloning a svn repo is impossible
On Thursday, September 27, 2012 6:30:48 PM UTC+2, Alexis Thongvan wrote: Hi, couldn't I just do : 1/git svn clone svn://adress/repo --stdlayout -r1:118 2/cd repo 3/git svn fetch -r 121:HEAD ? I don't know.. I suspect git-svn won't like it. Go ahead and try. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/t8TsJbQ1hSQJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] How do I create download packages on GitHub?
I would like to be able to create download packages (e.g. https://github.com/bobsilverberg/ValidateThis/downloads) for major releases of my project on GitHub, but can't figure out how to do it. Currently on my download page ( https://github.com/simonbingham/xindi/downloads) I have a single download button at the top of the page and no list of download packages. Can anyone help? -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/zOHlcRCBfJQJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] How do I create download packages on GitHub?
On Fri, 28 Sep 2012 08:56:07 -0700 (PDT) Simon Bingham smn...@gmail.com wrote: I would like to be able to create download packages (e.g. https://github.com/bobsilverberg/ValidateThis/downloads) for major releases of my project on GitHub, but can't figure out how to do it. Currently on my download page ( https://github.com/simonbingham/xindi/downloads) I have a single download button at the top of the page and no list of download packages. Can anyone help? I'm not sure what your complication is really about. I've just logged into my github account, navigated to my single project, clicked the Downloads tab and now I'm seeing the Upload new file box there which clearly offers me a way to upload a downloadable package. Isn't that what you're looking for? -- You received this message because you are subscribed to the Google Groups Git for human beings group. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
Re: [git-users] How do I create download packages on GitHub?
Can't believe I missed that. It is Friday afternoon though. Thank you. It seems a bit strange that you have to upload a file to create a new package when the code is already on GitHub. On Friday, 28 September 2012 17:12:47 UTC+1, Konstantin Khomoutov wrote: On Fri, 28 Sep 2012 08:56:07 -0700 (PDT) Simon Bingham smn...@gmail.com javascript: wrote: I would like to be able to create download packages (e.g. https://github.com/bobsilverberg/ValidateThis/downloads) for major releases of my project on GitHub, but can't figure out how to do it. Currently on my download page ( https://github.com/simonbingham/xindi/downloads) I have a single download button at the top of the page and no list of download packages. Can anyone help? I'm not sure what your complication is really about. I've just logged into my github account, navigated to my single project, clicked the Downloads tab and now I'm seeing the Upload new file box there which clearly offers me a way to upload a downloadable package. Isn't that what you're looking for? -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/khlqYtbvxcoJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] Re: Cloning a svn repo is impossible
yep, it does not work :/ Grafting is a bit too much for me yet (I barely understand how git works and I don't really know svn either) So I think I'm just going to clone from R121 -- You received this message because you are subscribed to the Google Groups Git for human beings group. To view this discussion on the web visit https://groups.google.com/d/msg/git-users/-/AS9AwqN3NhoJ. To post to this group, send email to git-users@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
[git-users] does git http backend work as in the manual?
following
http://www.kernel.org/pub/software/scm/git/docs/git-http-backend.html
I have the anonymous git clone work
if I set this
{{{
Location /git/private AuthType Basic AuthName Private Git Access
Require group committers ... /Location
}}}
that seems work.
but if I following the manual want anonymous download and authenticated write
like this
{{{
To enable anonymous read access but authenticated write access, require
authorization with a LocationMatch directive:
LocationMatch ^/git/.*/git-receive-pack$
AuthType Basic
AuthName Git Access
Require group committers
...
/LocationMatch
}}}
seems every time the server got
/git/info/refs?service=git-upload-pack HTTP/1.1 401 726
because of the question mark in the request uri, the regular expression
doesn't work, so it didn't ask me the password and give failure.
What I really want to do is like this:
separate user in two groups: dev and user
anonymous: no access, can not git clone
user group: can clone, but can not push, both require authentication
dev group: can clone and push. both require authentication
I was trying to use
LocationMatch ^/git/.*/git-receive-pack$
and for push
and use a
LocationMatch ^/git/.*/git-upload-pack$
for clone.
but because of those question mark, it doesn't work
Does anyone have good solution?
--
You received this message because you are subscribed to the Google Groups Git
for human beings group.
To view this discussion on the web visit
https://groups.google.com/d/msg/git-users/-/Yl4zm4M0JKAJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/git-users?hl=en.
Re: [git-users] “Ghost” commit
Thank you very much for the links. Actually I've read a few pages of the book recently… And I think I understand the part about blobs, trees, commits… But what I don't understand is… if I stage a file, edit it, and stage it again, the blob created during the first staging will be purged if I run git purge. That happens because no commit was made between the two “adds”/staging. Nothing refers to the first one (any more). I also get that if a commit is amended, we are not supposed to use the amended one… or reference it, as the intention of amending is replacing it… pretend the replaced commit never happened. What I don't understand (or see the reasons) is why the blob for the amended commit is not “purge-able”… If it's not listed there, I guess something is referencing to it, and I wonder what, as it seems only reflog is capable of show it. If I have A --- B and amend B, now I have A --- C, and B, as far as I know, is no longer listed as a child of A and doesn't have A as a parent. reflog shows B, but who is using B? I am able to checkout B if I know its SHA1 code, and I think it would be a bad idea… I don't know why B can't be purged then. On Friday, 28 September 2012 09:16:04 UTC+1, Konstantin Khomoutov wrote: On Thu, Sep 27, 2012 at 05:28:23AM -0700, Thiago Rossi wrote: [...] Not sure what dangling means. I mean, how it differs from orphans/not being referenced… In my current repository, b95cad5 has been replaced by b219846. Both have the same parent. But b95cad5 became “invisible” in most interfaces, including git log, gitk and GitX. This commit should be reachable from the reflog of your repository as amending the (tip) commit moved the HEAD in a non-linear way, so this has been recorded to the reflog. Read the `git reflog` manual for more info. In general, you should just absorb the fact that reaching for the commit replaced by `git commit --amend` is an *unusual* case, and providing for a way to routinely expose it in various parts of Git's user interface is odd. I mean, when you do `git commit --amend`, provided you read and understood its manual page, you expect that command to completely replace the commit you're amending, as if the original commit just did not exist in the first place. The fact the original commit is still there by the time `git commit --amend` completed is just an implementation detail of the Git storage backend which uses garbage collection. The reflog I mentioned above, while not being a recent addition, have not always been there (and it's usually disabled in bare repositories). I understand you might have complications understanding why amending a commit works like it works (that is, why the commit changes, I mean, it's SHA-1 changes). This is because the commit object consists of metadata and a reference to a tree object, representing the state of files associated with that commit. The metadata, among other things, records the date and time the commit was made, and the commit message. Observe, that even if you did not change anything in the commit while amending it (I bother to check if Git compares the new commit message with the original one), the commit date/time changes and hence changes the commit object and hence changes its SHA-1. Changing the tree referenced by the commit (say, adding a forgotten file) changes that tree's SHA-1 hash which is recorded in the commit object and hence changes the commit object itself. If you like to dabble in such technical subtleties to better understand your tools, I highly recommend to read Git from the bottom up [1], and if you do not feel quite confident about those SHA-1 hashes and why commit object reference tree objects and stuff, you could start from The Git Parable [2] -- it's probably the simplest introduction to the concepts and is very fun to read. Another aspect is that different people have different tastes and different ideas about how a VCS tool should work, and you might just dislike the (frivolous) ways in which Git treats unpushed history (and pushed, too, as you'll discover sometime). You then can just try to refrain from using `git commit --amend`. This won't help if you want to fix the commit message up [*], but if you forgot to add a file or want to remove a file, you might just record another commit doing exactly that. This is not considered to be a best practice, but you know better what works better for your workflow/approach. [*] For instance, Fossil, while not allowing rewriting history at all, would allow you to change the commit message, but it does this by recording a special artifact in the repository, and the original commit message is preserved for later inspection. As you can see, Git's developers have radically different idea about how to treat the unpublished history. 1.
