Re: [git-users] An equivalent of `--full-history` to git bisect
On Fri, Apr 22, 2016 at 5:29 PM, Dale R. Worley <wor...@alum.mit.edu> wrote: > Ram Rachum <ram.rac...@gmail.com> writes: > > Then, as I said in the beginning, a friend pointed me towards the > > `--full-history` flag: > > > > $ git log --full-history --graph coffee > > * commit 0aa833916e908ea93902a6c4c227f9a884a1bcef > > |\ Merge: cf02fbb 3068c7d > > | | Author: Ram Rachum <r...@rachum.com> > > | | Date: Tue Apr 19 17:44:31 2016 +0300 > > | | > > | | Merge branch 'master' into development > > | | > > | * commit 3068c7d2548f1798b6840f73b13a649937339f28 > > |/ Author: Ram Rachum <r...@rachum.com> > > | Date: Tue Apr 19 16:02:27 2016 +0300 > > | > > | Adding sugar to coffee > > | > > * commit cf02fbbc40104cd02eea4c7c6f134ef1fd7b5661 > > Author: Ram Rachum <r...@rachum.com> > > Date: Tue Apr 19 16:00:47 2016 +0300 > > > > Create coffee > > > > This makes me happy because it shows the two relevant commits, the one > > adding sugar and the merge that removed it. So my problem is solved. > **But > > I really wish I could know how to make `git bisect` as well.** Does > anyone > > happen to know? > > You have to be careful here. You *think* of commit 0aa833 as removing > sugar, but it only removes sugar with respect to commit 3068c7. It's > *other* parent doesn't have sugar, in fact, has the same file tree as > 0aa833. When you look at 0aa833 as a child of cf02fb, what you see is a > merge that didn't insert sugar that was present in the merged commit. > And if sugar was some debugging print that you added to the branch to > test it, you'd think of things the second way. > > The deep question is "What is the (linear) history of this commit?" You > *think* of the history being 0aa833-3068c7-cf02fbbc, but it's equally > valid to think of it as 0aa833-cf02fbbc. > > Now with regard to git-bisect, how do you define it? The binary search > for "Where was this introduced?" only makes sense along a linear path. > So which linear path should git-bisect choose through the directed > acyclic graph of commits? > The first thing you do with bisect is define a good commit (3068) and a bad commit (b7a8). Any linear path you draw between these two commits will land on the merge (which is the commit that you want to find.) I don't know which linear path git-bisect uses today, but I'm not seeing how it can use a linear path that skips the bad merge. In any case, it would be nice if it'll have an option similar to `--full-history` that'll make it not skip that merge. > > Dale > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Git for human beings" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/git-users/v3__t42qbKE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > git-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] An equivalent of `--full-history` to git bisect
Hi everyone!
I've been using Git heavily for about 7 years. A few days ago I found a
behavior that surprised me. I found `git log`, `git blame` and `git bisect`
to exhibit this weird behavior. [A friend][1] let me know about the
`--full-history` flag to `git log` that solved my problem, and another
person showed me that `--full-history` works for `git blame` too . I want
to know, for my own education, whether there is an equivalent fix for `git
bisect`.
Feel free to see the problem for yourself with this repo:
https://dl.dropboxusercontent.com/u/1927707/problematic_repo.7z
Here is its log:
$ git log --graph
* commit b7a8d7aa001d06eb7491ab5fb447a8dd3aa421a8
| Author: Ram Rachum <r...@rachum.com>
| Date: Tue Apr 19 17:45:01 2016 +0300
|
| adding more to some-file
|
* commit 0aa833916e908ea93902a6c4c227f9a884a1bcef
|\ Merge: 2413945 3068c7d
| | Author: Ram Rachum <r...@rachum.com>
| | Date: Tue Apr 19 17:44:31 2016 +0300
| |
| | Merge branch 'master' into development
| |
| * commit 3068c7d2548f1798b6840f73b13a649937339f28
| | Author: Ram Rachum <r...@rachum.com>
| | Date: Tue Apr 19 16:02:27 2016 +0300
| |
| | Adding sugar to coffee
| |
* | commit 24139451ab954b1f0a9ef616775a3dba0ac81669
|/ Author: Ram Rachum <r...@rachum.com>
| Date: Tue Apr 19 16:01:28 2016 +0300
|
| Creating some-file
|
* commit cf02fbbc40104cd02eea4c7c6f134ef1fd7b5661
Author: Ram Rachum <r...@rachum.com>
Date: Tue Apr 19 16:00:47 2016 +0300
Create coffee
In the very first commit, the file `coffee` was added. In the commit
`3068c7d`, I added a line "sugar" to the `coffee` file. But then I merged
this branch into the `development` branch, and in that merge, a mistake was
made and the "sugar" line was removed, leaving `coffee` empty. Then another
commit `b7a8d7a`, making an unrelated change, was added for good measure.
Now I'm looking at my coffee, and finding there's no sugar in it. I
distinctly remember adding sugar to my coffee. I run `git log coffee`, and
get this output:
$ git log coffee
commit cf02fbbc40104cd02eea4c7c6f134ef1fd7b5661
Author: Ram Rachum <r...@rachum.com>
Date: Tue Apr 19 16:00:47 2016 +0300
Create coffee
That's it. `git log` is showing neither my original commit that added the
sugar, nor the merge that removed it. Two very relevant commits that are
missing.
I was frustrated for about an hour by this problem, because it happened in
a huge enterprise repo, where commits are much harder to find manually.
I also tried using `git bisect` to pin down the two commits, but it pointed
me to the wrong commit after I finished doing all the `git bisect bad` and
`git bisect good` actions.
Then, as I said in the beginning, a friend pointed me towards the
`--full-history` flag:
$ git log --full-history --graph coffee
* commit 0aa833916e908ea93902a6c4c227f9a884a1bcef
|\ Merge: cf02fbb 3068c7d
| | Author: Ram Rachum <r...@rachum.com>
| | Date: Tue Apr 19 17:44:31 2016 +0300
| |
| | Merge branch 'master' into development
| |
| * commit 3068c7d2548f1798b6840f73b13a649937339f28
|/ Author: Ram Rachum <r...@rachum.com>
| Date: Tue Apr 19 16:02:27 2016 +0300
|
| Adding sugar to coffee
|
* commit cf02fbbc40104cd02eea4c7c6f134ef1fd7b5661
Author: Ram Rachum <r...@rachum.com>
Date: Tue Apr 19 16:00:47 2016 +0300
Create coffee
This makes me happy because it shows the two relevant commits, the one
adding sugar and the merge that removed it. So my problem is solved. **But
I really wish I could know how to make `git bisect` as well.** Does anyone
happen to know?
[1]: http://www.syntevo.com/smartgithg/
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Pushing a rebased branch without --force
I read the documentation a few more times and now I understand. It's not a complete solution but a partial one, but it's still helpful I guess that's the best I can get right now. Thanks for your help Konstantin. On Thu, Sep 3, 2015 at 8:10 PM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Thu, 3 Sep 2015 19:45:11 +0300 > Ram Rachum <ram.rac...@gmail.com> wrote: > > [...] > > I'm really lost in your reply. I had a problem: I want to have a push > > command that (1) works even after a rebase and (2) refuses to push > > when there's a new commit in the remote branch that doesn't exist in > > the local branch. I thought you suggested that `--force-with-lease` > > is a solution. Currently it seems to fail requirement 2, so there's > > no point in talking about requirement 1, so there's no point in > > talking about rebasing at all. > > > > Is there a way to use `--force-with-lease` so it satisfies > > requirement 2? If you want me to try arguments, then which arguments? > > (Sorry I'm too lost to understand which arguments I should put there.) > > OK, let's have a clean start. > > Did you read the documentation on --force-with-lease? > If no, please do (it's in the manual page describing `git push`). > If yes, then did you understand how exactly this option modifies the > behaviour of `git push` in all three modes this option can be used? > If no, then which exactly bits caused trouble? > > To be clear, I did not use --force-with-lease myself as I don't have > use cases for it but I think I'm able to get you going with using it > *if* you're willing to learn and try things out. By now, unfortunately, > it looks like you don't want to invest into understanding this stuff > and instead want someone to give you a ready working solution. If yes, > I'm out, and you might consider asking on StackOverflow or whatnot. > You might also ask on the main Git list but please make sure you have > read [1] and understood the requirements which are there for posting > to that list to succeed. > > 1. https://gist.github.com/tfnico/4441562 > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Pushing a rebased branch without --force
On Thu, Sep 3, 2015 at 6:58 PM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Thu, 3 Sep 2015 05:17:34 -0700 (PDT) > Ram Rachum <ram.rac...@gmail.com> wrote: > > > Is there a way to avoid this? (Aside from pre-checking manually on > > the repo using `git fetch`.) I want something like `push --force` > > except it doesn't discard actual commits, only commits that have been > > reordered due to rebasing. > > Yes, since some version `git push` learned the --force-with-lease > command-line option which does just what you want: makes sure the tip > of the existing branch is exactly what you expect it to be. > Hi Konstantin, I was very happy to see this portion of your message because I figured you found a solution to my problem, but I tried it now and it didn't work. It pushes alright, but it happily runs over other changes that were pushed to the remote. I had a situation like this: http://i.imgur.com/sn8oScu.jpg Then ran this: $ git push origin test-lease --force-with-lease Counting objects: 2, done. Delta compression using up to 4 threads. Compressing objects: 100% (2/2), done. Writing objects: 100% (2/2), 244 bytes | 0 bytes/s, done. Total 2 (delta 1), reused 0 (delta 0) To [REDACTED] f7127f4..282393a test-lease -> test-lease Then I got this: http://i.imgur.com/7iq5qRJ.jpg So as you can see, the commit f7127 was thrown away. Perhaps I misunderstood how `--force-with-lease` is supposed to work? Thanks, Ram. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Pushing a rebased branch without --force
On Thu, Sep 3, 2015 at 7:37 PM, Konstantin Khomoutov < flatw...@users.sourceforge.net> wrote: > On Thu, 3 Sep 2015 19:16:23 +0300 > Ram Rachum <ram.rac...@gmail.com> wrote: > > [...] > > > Yes, since some version `git push` learned the --force-with-lease > > > command-line option which does just what you want: makes sure the > > > tip of the existing branch is exactly what you expect it to be. > > > > I was very happy to see this portion of your message because I > > figured you found a solution to my problem, but I tried it now and it > > didn't work. It pushes alright, but it happily runs over other > > changes that were pushed to the remote. > > > > I had a situation like this: http://i.imgur.com/sn8oScu.jpg > > > > Then ran this: > > > > $ git push origin test-lease --force-with-lease > > Counting objects: 2, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (2/2), done. > > Writing objects: 100% (2/2), 244 bytes | 0 bytes/s, done. > > Total 2 (delta 1), reused 0 (delta 0) > > To [REDACTED] > >f7127f4..282393a test-lease -> test-lease > > > > Then I got this: http://i.imgur.com/7iq5qRJ.jpg > > > > So as you can see, the commit f7127 was thrown away. > > > > Perhaps I misunderstood how `--force-with-lease` is supposed to work? > > The documentation says that the unadorned --force-with-lease looks at > the remote-tracking branch for the target ref (a branch in your case), > if this exists, and requires the tip of the target ref to be the same > as the tip of this remote-tracking branch. > > IOW, if you're pushing to "test-lease" with plain --force-with-lease, > `git push` will try to locate the "remotes/origin/test-lease" branch > and then require that the remote "test-lease" branch points to the same > commit your "remotes/origin/test-lease" points to. > > This means that if you did rebase your local "test-lease" and then > did `git fetch`, you've updated your "remotes/origin/test-lease" > with the current "upstream" tip commit of that branch and the check > passed when you pushed. > > So, could you somehow verify that? > > You could also try the two argument form of --force-with-lease. > I'm really lost in your reply. I had a problem: I want to have a push command that (1) works even after a rebase and (2) refuses to push when there's a new commit in the remote branch that doesn't exist in the local branch. I thought you suggested that `--force-with-lease` is a solution. Currently it seems to fail requirement 2, so there's no point in talking about requirement 1, so there's no point in talking about rebasing at all. Is there a way to use `--force-with-lease` so it satisfies requirement 2? If you want me to try arguments, then which arguments? (Sorry I'm too lost to understand which arguments I should put there.) Thanks, Ram. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[git-users] Pushing a rebased branch without --force
Hi, I've been using Git for years, but only recently I started working for a big company where they use `git rebase` to maintain a linear history. One problem I have with this is that when I rebase a branch, I can't push it to the remote again, I have to use `--force` because the remote has a different history, before the rebase. I don't like this because using `--force` means that if there were more commits in that remote that weren't pulled, they'd be garbage-collected! Is there a way to avoid this? (Aside from pre-checking manually on the repo using `git fetch`.) I want something like `push --force` except it doesn't discard actual commits, only commits that have been reordered due to rebasing. Thanks, Ram. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [git-users] Keeping IDE files in a public project
Cool, I think I'll use something like this. (Except that I'll do `merge --squash` to merge back my changes.) Thanks Dale and Gergely! On Mon, Mar 25, 2013 at 5:24 PM, Dale R. Worley wor...@alum.mit.edu wrote: One approach might be to keep one set of branches that have your IDE files, and one set of branches that don't. Something like: 1. remote tracking branch from the authoritative repository 2. your working branch, without IDE files 3. your working branch(es), with IDE files You work in #3. Changes can be moved from #2 to #3 can be done with ordinary merging. Changes can be moved from #3 to #2 using something like git filter-tree (presumably controlled by a version-controlled file that tells what to leave out). Dale -- You received this message because you are subscribed to a topic in the Google Groups Git for human beings group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/git-users/xT3DLs2pqPw/unsubscribe?hl=en-US . To unsubscribe from this group and all its topics, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[git-users] Keeping IDE files in a public project
Hi everybody, Here's a problem I had to deal with many times. I'm hoping someone here can come up with a solution. I'm working on an open-source project. I need to have a few files that other people wouldn't like to see: Mostly IDE files. I don't want to commit those files to the repo itself, because other developers usually don't like that. However, I wouldn't like to ignore them either, because I want those file source-controlled for all the advantages that this provides. (Great backup, versioning, etc.) I work on multiple computers so when I update these files on one computer, I want to be able to check them out on the other computer like I normally do with Git. How can I solve this problem? My idea is to have my own repo that contains the open-source project as a submodule, but I've never tried that and I don't know whether it will work and be convenient to work with. I'll be happy to hear suggestions on what to do. Thanks, Ram. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] Keeping IDE files in a public project
Gergerly, that doesn't solve my problem. I want the files to be saved for me to be able to use them on any computer in which I work on the repo. On Sat, Mar 23, 2013 at 12:39 AM, Gergely Polonkai gerg...@polonkai.euwrote: That depends on your IDE. E.g. Netbeans cat store the project (IDE) files in a separate directory, and as I remember, Eclipse can do the same. On 22 March 2013 23:22, Ram Rachum ram.rac...@gmail.com wrote: Hi everybody, Here's a problem I had to deal with many times. I'm hoping someone here can come up with a solution. I'm working on an open-source project. I need to have a few files that other people wouldn't like to see: Mostly IDE files. I don't want to commit those files to the repo itself, because other developers usually don't like that. However, I wouldn't like to ignore them either, because I want those file source-controlled for all the advantages that this provides. (Great backup, versioning, etc.) I work on multiple computers so when I update these files on one computer, I want to be able to check them out on the other computer like I normally do with Git. How can I solve this problem? My idea is to have my own repo that contains the open-source project as a submodule, but I've never tried that and I don't know whether it will work and be convenient to work with. I'll be happy to hear suggestions on what to do. Thanks, Ram. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Git for human beings group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/git-users/xT3DLs2pqPw/unsubscribe?hl=en-US . To unsubscribe from this group and all its topics, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] Keeping IDE files in a public project
And this will be more convenient than a submodule? On Sat, Mar 23, 2013 at 1:24 AM, Gergely Polonkai gerg...@polonkai.euwrote: If you manage to store them in a different directory, it will be easy to manage them in a your own repository. E.g you check out the project source in /home/user/project/source from git.project.com and the IDE files to /home/user/project/ide from git.example.com, and combine them by using the IDE's powers :) On 22 March 2013 23:47, Ram Rachum r...@rachum.com wrote: Gergerly, that doesn't solve my problem. I want the files to be saved for me to be able to use them on any computer in which I work on the repo. On Sat, Mar 23, 2013 at 12:39 AM, Gergely Polonkai gerg...@polonkai.euwrote: That depends on your IDE. E.g. Netbeans cat store the project (IDE) files in a separate directory, and as I remember, Eclipse can do the same. On 22 March 2013 23:22, Ram Rachum ram.rac...@gmail.com wrote: Hi everybody, Here's a problem I had to deal with many times. I'm hoping someone here can come up with a solution. I'm working on an open-source project. I need to have a few files that other people wouldn't like to see: Mostly IDE files. I don't want to commit those files to the repo itself, because other developers usually don't like that. However, I wouldn't like to ignore them either, because I want those file source-controlled for all the advantages that this provides. (Great backup, versioning, etc.) I work on multiple computers so when I update these files on one computer, I want to be able to check them out on the other computer like I normally do with Git. How can I solve this problem? My idea is to have my own repo that contains the open-source project as a submodule, but I've never tried that and I don't know whether it will work and be convenient to work with. I'll be happy to hear suggestions on what to do. Thanks, Ram. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Git for human beings group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/git-users/xT3DLs2pqPw/unsubscribe?hl=en-US . To unsubscribe from this group and all its topics, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Git for human beings group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/git-users/xT3DLs2pqPw/unsubscribe?hl=en-US . To unsubscribe from this group and all its topics, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [git-users] Keeping IDE files in a public project
If the open-source project's repository is a submodule of my own, wouldn't that work? On Sat, Mar 23, 2013 at 1:32 AM, Gergely Polonkai gerg...@polonkai.euwrote: Submodules are committed with the project, so your fellow developers would see that they exist. Also, submodules need to be committed separately, while the approach I described can be automated with software like SparkleShare (if you don't mind that you don't control the commit messages) On 23 March 2013 00:28, Ram Rachum r...@rachum.com wrote: And this will be more convenient than a submodule? On Sat, Mar 23, 2013 at 1:24 AM, Gergely Polonkai gerg...@polonkai.euwrote: If you manage to store them in a different directory, it will be easy to manage them in a your own repository. E.g you check out the project source in /home/user/project/source from git.project.com and the IDE files to /home/user/project/ide from git.example.com, and combine them by using the IDE's powers :) On 22 March 2013 23:47, Ram Rachum r...@rachum.com wrote: Gergerly, that doesn't solve my problem. I want the files to be saved for me to be able to use them on any computer in which I work on the repo. On Sat, Mar 23, 2013 at 12:39 AM, Gergely Polonkai gerg...@polonkai.eu wrote: That depends on your IDE. E.g. Netbeans cat store the project (IDE) files in a separate directory, and as I remember, Eclipse can do the same. On 22 March 2013 23:22, Ram Rachum ram.rac...@gmail.com wrote: Hi everybody, Here's a problem I had to deal with many times. I'm hoping someone here can come up with a solution. I'm working on an open-source project. I need to have a few files that other people wouldn't like to see: Mostly IDE files. I don't want to commit those files to the repo itself, because other developers usually don't like that. However, I wouldn't like to ignore them either, because I want those file source-controlled for all the advantages that this provides. (Great backup, versioning, etc.) I work on multiple computers so when I update these files on one computer, I want to be able to check them out on the other computer like I normally do with Git. How can I solve this problem? My idea is to have my own repo that contains the open-source project as a submodule, but I've never tried that and I don't know whether it will work and be convenient to work with. I'll be happy to hear suggestions on what to do. Thanks, Ram. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Git for human beings group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/git-users/xT3DLs2pqPw/unsubscribe?hl=en-US . To unsubscribe from this group and all its topics, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Git for human beings group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/git-users/xT3DLs2pqPw/unsubscribe?hl=en-US . To unsubscribe from this group and all its topics, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to a topic in the Google Groups Git for human beings group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/git-users/xT3DLs2pqPw/unsubscribe?hl=en-US . To unsubscribe from this group and all its topics, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups Git for human beings group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
