Perl 6 - the future is here, just unevenly distributed

IRC log for #git, 2016-11-26

| Channels | #git index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:00 m0viefreak joined #git
00:07 Akardi joined #git
00:09 LBV_User joined #git
00:13 buzzLightBeer joined #git
00:20 rebrec joined #git
00:21 d0nn1e joined #git
00:23 rebrec joined #git
00:26 SwiftMatt joined #git
00:26 theskillwithin joined #git
00:27 svm_invictvs joined #git
00:28 ash_workz joined #git
00:30 agileadam joined #git
00:31 chibby0ne left #git
00:32 nikivi joined #git
00:35 lwf joined #git
00:35 pnorman joined #git
00:37 jimi_ joined #git
00:38 pnorman I want to edit an earlier commit, not yet pushed anywhere yet. The only issue I have is that it's the first commit of the repository, so git rebase -i isn't working. It's a fairly trivial fix I want to do.
00:39 ToBeCloud joined #git
00:39 SwiftMatt joined #git
00:39 cbreak pnorman: rebase has a special command line flag to rebase the root commit
00:40 cbreak it's called --root :)
00:41 pnorman thanks
00:45 wxg joined #git
00:46 rorro joined #git
00:47 adac joined #git
00:50 venmx joined #git
00:51 arescorpio joined #git
00:54 ResidentBiscuit joined #git
00:56 safe joined #git
00:57 phos1 joined #git
00:58 phos1 Any suggsetions for an Issue tracking? I use phpstorm. I’ve been looking at visual studio (Can’t organize time across projects), and a few others. Small team, I want the project manager to be able to sort / priortize tasks for everyone. Any suggestions
01:04 ResidentBiscuit Trello is nice. Doesn't force you into any particular workflow
01:04 [ADN] joined #git
01:05 pnorman left #git
01:05 overlord_tm joined #git
01:06 _ADN_ joined #git
01:08 cagedwisdom joined #git
01:15 SwiftMatt joined #git
01:24 cagedwisdom joined #git
01:28 davimore__ joined #git
01:30 jaguarmagenta joined #git
01:34 austin987 joined #git
01:38 yaewa joined #git
01:47 Orbitrix joined #git
01:47 Orbitrix joined #git
01:48 Orbitrix joined #git
01:51 venmx joined #git
01:51 moei joined #git
01:55 jaguarmagenta joined #git
02:02 smithbone joined #git
02:02 ericP joined #git
02:05 yaewa joined #git
02:05 prg3 joined #git
02:06 finalbeta joined #git
02:09 HoierM joined #git
02:10 ResidentBiscuit joined #git
02:11 zulutango joined #git
02:13 gmn8719 joined #git
02:13 moei joined #git
02:16 snthsnth joined #git
02:18 d^sh joined #git
02:27 pks joined #git
02:32 Vinnie_win joined #git
02:33 Sasazuka joined #git
02:33 Vampire0 joined #git
02:49 ilbot3 joined #git
02:49 Topic for #git is now Welcome to #git, the place for git help and serious business | Public logs at http://jk.gs/glog | First visit? Read: http://jk.gs/git | Current stable version: 2.10.2 | Getting "cannot send to channel"? /msg gitinfo .voice | The git-jokes project has been suspended for lack of contribution. Help revive it! https://madeitwor.se/git-jokes
02:52 wgrant joined #git
02:52 venmx joined #git
02:53 julius_ joined #git
02:55 zulutango joined #git
02:57 SwiftMatt joined #git
03:06 fahadash joined #git
03:10 chachasmooth joined #git
03:15 hexagoxel joined #git
03:15 Goplat joined #git
03:22 WizJin joined #git
03:23 JamesBaxter joined #git
03:24 arand__ joined #git
03:31 fuzzmz joined #git
03:31 Darren_ joined #git
03:32 archaic joined #git
03:38 Gamecubic joined #git
03:42 buffal0 joined #git
03:45 sunri5e joined #git
03:45 CrazyBonz joined #git
03:45 moei joined #git
03:48 rchavik joined #git
03:51 SwiftMatt joined #git
03:52 nicksloan joined #git
03:53 Urbany joined #git
03:53 Dougie187 joined #git
03:53 venmx joined #git
03:56 Boniche joined #git
03:59 justanotheruser joined #git
04:08 ochorocho__ joined #git
04:13 raspado joined #git
04:14 Vortex35 joined #git
04:14 nowhere_man joined #git
04:14 donmichelangelo joined #git
04:20 nicksloa_ joined #git
04:21 cagedwisdom joined #git
04:21 justan0theruser joined #git
04:22 Sasazuka joined #git
04:23 romerocesar joined #git
04:25 Rodya_ joined #git
04:27 railssmith joined #git
04:30 mizu_no_oto joined #git
04:38 MrWoohoo joined #git
04:39 ugjka joined #git
04:44 fstd_ joined #git
04:45 giraffe joined #git
04:49 Nilesh_ joined #git
04:52 ThunderChicken joined #git
04:52 ThunderChicken joined #git
04:54 venmx joined #git
04:57 SwiftMatt joined #git
04:58 qws-user-1229 joined #git
05:00 krillr joined #git
05:05 jaguarmagenta joined #git
05:08 systmkor joined #git
05:08 Aces_Charles joined #git
05:09 pikajude joined #git
05:09 Cabanossi joined #git
05:11 srcerer_ joined #git
05:11 shampine joined #git
05:14 oxsyn joined #git
05:22 cagedwisdom joined #git
05:22 dirtyroshi_ joined #git
05:23 cagedwisdom joined #git
05:24 cagedwisdom joined #git
05:27 a_thakur joined #git
05:34 phanimahesh joined #git
05:39 ronny joined #git
05:39 dirtyroshi_ joined #git
05:44 Rarglepuff joined #git
05:49 louipc joined #git
05:50 Siegfried joined #git
05:53 louipc sweet
05:55 venmx joined #git
05:55 JanC_ joined #git
05:59 Rarglepuff left #git
06:06 louipc left #git
06:06 wrouesnel joined #git
06:09 aidalgol joined #git
06:12 Gloomy joined #git
06:12 azerus joined #git
06:14 cagedwisdom joined #git
06:15 NeverTired joined #git
06:28 snthsnth joined #git
06:30 Vangelis_ joined #git
06:33 tnecniv joined #git
06:33 tnecniv hello. i accidentally commited some big files. i deleted them via git rm but they still exist in the repo
06:34 tnecniv this is problematic for uploading to github
06:34 tnecniv how should i remove them?
06:35 preaction !sensitive
06:35 gitinfo [!filter_sensitive] You can use filter-branch to remove sensitive data from a repository's history. https://help.github.com/arti​cles/remove-sensitive-data/
06:35 preaction tnecniv: see what gitinfo said
06:35 qt-x joined #git
06:39 tnecniv thanks!
06:39 BlessJah tnecniv: assuming that big file have been commited N commits ago, and not yet published, it will be easier to use git reset --soft
06:40 BlessJah git reset soft <hash that intorduced bigfile>~
06:40 hahuang65 joined #git
06:40 tnecniv BlessJah well i already fixed it with that link so
06:40 * tnecniv shrugs
06:40 BlessJah ok then
06:44 pijiu joined #git
06:45 pijiu joined #git
06:47 A5101 joined #git
06:47 pijiu joined #git
06:47 nilukush_ joined #git
06:48 pijiu joined #git
06:51 ochorocho__ joined #git
06:55 LucaTM joined #git
06:56 venmx joined #git
06:56 Darren_ joined #git
06:58 bocaneri joined #git
07:03 shams joined #git
07:07 eblip joined #git
07:08 basiclaser joined #git
07:14 ShekharReddy joined #git
07:18 Sasazuka joined #git
07:19 ejnahc joined #git
07:26 MrMojito joined #git
07:29 SwiftMatt joined #git
07:30 Guest68411 joined #git
07:31 xall joined #git
07:37 subhojit777 joined #git
07:42 Mobutils joined #git
07:46 rooftopjoe joined #git
07:46 cagedwisdom joined #git
07:47 breezy_ joined #git
07:47 ayjay_t joined #git
07:47 rooftopjoe hi. out of curiosity, is there a git command that adds/removes things to/from .gitignore? i know i can manually edit the file and that's what i've been doing but i'm just curious.
07:49 dreiss joined #git
07:50 HedgeMage Not to my knowledge, rooftopjoe
07:51 _ikke_ Nope
07:52 justan0theruser joined #git
07:53 rooftopjoe also... is there any way to modify a past commit? (is that what rebasing would do for me?)
07:53 rooftopjoe legal reasons
07:53 overlord_tm joined #git
07:53 rooftopjoe there's something that should not exist in there any longer, in any shape or form
07:54 _ikke_ rooftopjoe: Modifying commits in git means creating a new commit and all commits following
07:54 _ikke_ rooftopjoe: rebase can do it
07:54 adac joined #git
07:54 HedgeMage rooftopjoe: Yes, but it's complicated and git's integrity checking means that it will not be transparent.
07:55 HedgeMage rooftopjoe: depending on what's being removed and how much it pervades the history, a remove and rebase could be sufficient, or you may have to resort to serious editing with reposurgeon
07:55 rooftopjoe in which way will it not be transparent? i don't mind if someone can see i did a rebase, i just don't want them to be able to see a certain commit
07:55 _ikke_ rooftopjoe: Do they already have that commit?
07:56 HedgeMage I mean that they will know something has changed, and they will have to re-clone to avoid merge hell, because (assuming they've already seen stuff that happened after that commit) commit hashes will change.
07:56 rooftopjoe the commit exists in the repo but our legal department discovered a software patent yotta yotta
07:57 rooftopjoe HedgeMage: so in a sense the repo will not be in sync with other local repositories. but someone who has never cloned would have no idea anything changed.
07:58 rooftopjoe that's what i understand.
07:59 HedgeMage rooftopjoe: right
07:59 rooftopjoe thanks. i will read how to rebase
07:59 HedgeMage rooftopjoe: I've had to do sanitizing like this for confidential data somebody accidentally committed, so if you get in over your head, ping and I'll point you at some tools/menthods
08:00 HedgeMage (life of an infosec geek)
08:00 _ikke_ !sensitive
08:00 gitinfo [!filter_sensitive] You can use filter-branch to remove sensitive data from a repository's history. https://help.github.com/arti​cles/remove-sensitive-data/
08:00 _ikke_ Here is a guide
08:00 rooftopjoe it's a single commit that doesn't affect much else, i don't think i need any special tools
08:01 HedgeMage cool.
08:01 venmx joined #git
08:01 rooftopjoe so although it's a linear history, i guess the only thing that makes a rebase obvious is that an old commit has a newer date
08:02 rooftopjoe C1 -> C2, where C1 happened after C2
08:02 _ikke_ All commit dates change
08:02 rooftopjoe oh
08:02 _ikke_ author dates won't
08:02 rooftopjoe what's an author date? (sorry, newbie)
08:02 _ikke_ Each commit has a author + date and comitter + date
08:03 Seveas git stores two sets of user information per commit: one for author and one for committer. Those can be two different people
08:03 Seveas e.g. when you rebase someone else's commits, they stay the author, but you become the committer
08:03 rooftopjoe that makes sense. it's probably what happens when you push/pull as well.
08:03 _ikke_ No
08:04 _ikke_ push/pull cannot change commits
08:04 rooftopjoe i meant reagarding the author/committer
08:04 rooftopjoe i expect the comitter is the one who pulled
08:04 _ikke_ Nope
08:04 rooftopjoe and the author is the original author
08:04 rooftopjoe ah, ok
08:04 rooftopjoe i should maybe read instead of making guesses
08:04 _ikke_ WHen you change either committer or author, the hash of the commit changes
08:05 _ikke_ !book
08:05 gitinfo There are several good books available about git; 'Pro Git' is probably the best: http://git-scm.com/book but also look at !bottomup !cs !gcs !designers !gitt !vcbe and !parable
08:05 rooftopjoe ty
08:06 rooftopjoe i don't even want to imagine the pain of rebasing something that's used as a submodule
08:06 pikajude joined #git
08:07 _ikke_ It means updating the recorded commit
08:07 rooftopjoe oh, that's a fair point
08:10 Siegfried joined #git
08:11 Mobutils joined #git
08:15 qws-user-1228 joined #git
08:15 hhee joined #git
08:24 snthsnth joined #git
08:24 julius_ joined #git
08:26 pks joined #git
08:26 Anja joined #git
08:31 byte512 joined #git
08:36 pks joined #git
08:38 DaVu joined #git
08:39 leeN joined #git
08:40 mischat joined #git
08:40 hahuang65 joined #git
08:40 mischat joined #git
08:40 menip joined #git
08:42 jknetl joined #git
08:42 DaVu Good morning. Just a little beginner question. I have my own fork of a repo. My "master" (from my fork) is on the same state as the "master" I forked from. I created a branch on my fork some days ago. What should I do, if I want that branch on the same state as the master but still being a seperated branch?
08:48 root joined #git
08:48 dodobrain joined #git
08:50 enleeten joined #git
08:50 dodobrain joined #git
08:50 venmx joined #git
08:59 Nilesh_ joined #git
08:59 xall joined #git
09:06 inflames joined #git
09:07 diogenese joined #git
09:08 mischat joined #git
09:08 vuoto joined #git
09:08 mischat joined #git
09:09 vrlx joined #git
09:12 _ikke_ git reset --keep master while you are on that branch
09:14 DaVu _ikke_: thanks
09:14 Siegfried joined #git
09:14 vuoto joined #git
09:15 re1 joined #git
09:16 derk0pf joined #git
09:16 grayjoc joined #git
09:19 venmx joined #git
09:21 anddam when cloning from a git@github.com: URI I get a repository whose origin URLs are http://  is this normal? shouldn't I get a git@ one instead?
09:24 glebihan_ joined #git
09:25 cagedwisdom joined #git
09:28 cagedwisdom joined #git
09:30 harrymoreno joined #git
09:32 cdown joined #git
09:34 shinnya joined #git
09:37 holgersson joined #git
09:39 mischat joined #git
09:39 cagedwisdom joined #git
09:40 PCatinean joined #git
09:43 venmx joined #git
09:44 cagedwisdom joined #git
09:47 cagedwisdom joined #git
09:48 cagedwisdom joined #git
09:49 julius_ joined #git
09:49 venmx joined #git
09:50 cagedwisdom joined #git
10:00 afuentes joined #git
10:03 rbern joined #git
10:03 lindenle joined #git
10:06 mmlb joined #git
10:06 julius_ joined #git
10:13 mischat joined #git
10:15 rebrec joined #git
10:18 robattila256 joined #git
10:18 _ikke_ anddam: You can choose either http or ssh
10:18 _ikke_ Both work
10:18 _ikke_ but ssh keys only work with ssh of course
10:19 osse git:// also works, i think
10:19 robotroll joined #git
10:19 _ikke_ Yes, but only for cloning / fetching
10:20 osse oui, monsieur
10:20 _ikke_ You can even use svn if that floats your boat :P
10:24 holgersson joined #git
10:27 PCatinean Hey guys
10:27 PCatinean I have 3 commits and I would like to squash the 3rd one into the 1st
10:27 PCatinean how can I do that?
10:27 j416 PCatinean: use interactive rebase man git-rebase
10:27 gitinfo PCatinean: the git-rebase manpage is available at http://jk.gs/git-rebase.html
10:28 PCatinean j416, i;m in it
10:28 adac joined #git
10:28 PCatinean do I simply change the rder of the commits?
10:28 j416 yes
10:28 PCatinean change the order of the first to second and put S on the 3rd?
10:28 j416 PCatinean: read the text under
10:29 j416 PCatinean: put them in the order you want them
10:30 j416 PCatinean: the commit you want to squash goes under the one you want to squash it into
10:31 tvw joined #git
10:32 cdown joined #git
10:32 svm_invictvs joined #git
10:32 PCatinean ahh got it thanks
10:32 PCatinean damn I just put them in another commit
10:32 PCatinean I needed to go two more up
10:32 j416 PCatinean: ORIG_HEAD holds the previous state, you can reset back to that
10:33 osse ORIG_HEAD works with rebase? :O
10:33 j416 that's what I use it for
10:33 j416 what else does it work with? :D
10:33 osse merge/pull
10:33 PCatinean git reset ORIG_HEAD ?
10:33 _ikke_ Linus Torvalds rarely uses the reflog, he uses ORIG_HEAD instead
10:34 j416 PCatinean: yes, should work
10:34 qws-user-1228 joined #git
10:34 j416 _ikke_: sounds like you're describing me
10:34 _ikke_ ok
10:34 _ikke_ I never think about ORIG_HEAD
10:34 j416 osse: never thought about it working with merge
10:34 _ikke_ git reset @{1} is easier :P
10:34 j416 merges are easy to undo; I suppose you could undo an ff-merge easily with it
10:35 j416 _ikke_: yeah
10:35 j416 I guess :)
10:35 j416 what's the difference between @{1} and @{-1} ?
10:36 _ikke_ j416: "The construct @{-<n>} means the <n>th branch/commit checked out before the current one."
10:36 j416 yeah so I already read that but I don't get it
10:37 j416 is @{<n>} local for the current branch and @{-<n>} for HEAD?
10:37 eivarv joined #git
10:37 PCatinean pfu thanks guys
10:37 PCatinean I think I will just keep them as they were
10:38 j416 o/
10:38 osse are you giving up?
10:39 PCatinean hmm, the extra commit isn't THAT bad
10:39 _ikke_ j416: @{1} just follows the reflog entries for the current branch
10:39 PCatinean Just thought I would not mess it up any worse
10:39 _ikke_ j416: @{-1} does some extra magic to actually find a branch
10:40 j416 _ikke_: so @{-1} is equal to - (for the commands that support it)?
10:40 _ikke_ j416: yeah, - is a shortcut for @{-1}
10:40 j416 TIL
10:41 j416 thanks
10:41 satifant joined #git
10:42 j416 is @{-1} equal to HEAD@{1} ?
10:42 _ikke_ Not necessarily
10:43 _ikke_ HEAD@{<n>} just tracks what commits HEAD has been on
10:43 _ikke_ But you can make several commits without changing HEAD@{-1}
10:43 j416 ooh, so it maps to branches
10:43 j416 that's the differene
10:43 j416 c
10:43 _ikke_ More or less
10:44 j416 well, checked out things
10:44 _ikke_ If you explicitly checkout a commit, then it would go back to that commit
10:44 j416 yeah, noticed
10:48 rebrec joined #git
10:48 zeroed joined #git
10:48 zeroed joined #git
10:50 seishun joined #git
10:50 subhojit777 joined #git
10:52 netj joined #git
10:58 pks joined #git
10:58 dsdeiz joined #git
11:02 newbie joined #git
11:04 Dragonbird joined #git
11:10 jaguarmagenta joined #git
11:12 nd joined #git
11:13 IPXSam joined #git
11:14 IPXSam Hello, how can I avoid the passphrase being asked every time I clone something and every time I push something?
11:14 IPXSam Is there a way to add a cooldown or something?
11:14 osse IPXSam: if you actually mean passphrase then that's an SSH thing
11:14 osse your ssh key has a passphrase
11:15 osse you can use GIT_SSH and GIT_SSH_COMMAND variables to customize how git invokes ssh
11:16 anddam _ikke_, osse: oh, I didn't figured I wasn't actually specifying the protocol with git@github.com
11:16 IPXSam Yeah the passphrase, so what you are saying is that git can be configured so that it asks less or should I  configure ssh to ask for it less?
11:16 anddam that's just the username
11:17 osse IPXSam: I expect that Git can't do anything about it. But if you know how to invoke ssh to get what you want then you can make git invoke it in the same way
11:19 IPXSam I don't know how to invoke SSH, basically I have no idea about what's going on
11:19 osse IPXSam: where is your repos hosted?
11:19 IPXSam github
11:20 osse IPXSam:  ssh -T git@github.com
11:20 osse that asks for a passphrase, yes ?
11:20 IPXSam it does
11:20 Bombe Is there a way to squelch the warning for an unset push.default without explicitely setting it?
11:21 osse IPXSam: ssh --magic-flag -T git@github.com. IF that works then  you can do export GIT_SSH_COMMAND='ssh --magic-flag'
11:21 osse Problem is that I don't know what --magic-flag is
11:22 vjoba joined #git
11:22 osse Alternatively, create a new key without a passphrase and use that.
11:22 IPXSam osse, unknown option
11:22 vjoba left #git
11:23 osse i didn't mean it literally
11:23 anddam it should change on its own
11:23 IPXSam oh..
11:23 Puffball joined #git
11:23 anddam that's the beauty of magic
11:23 IPXSam so you don't remember the flag?
11:24 osse I don't even know whether it exists
11:24 osse I don't know how to fix it. I am just telling you that once you figure it out you can tell Git about it
11:24 osse man ssh. see the SSH_ASKPASS environment variable. maybe that's useful. Or ask #openssh
11:25 osse I personally would create a new key because i am lazy
11:25 Bombe Okay, disregard my question, recently manipulated PATH resulted in an older version of Git being used.
11:28 Jackneill joined #git
11:31 pijiu joined #git
11:32 nikivi joined #git
11:34 anddam IPXSam: did you set up an ssh key with github?
11:35 IPXSam anddam, I did
11:35 anddam IPXSam: I guess your origin is http:// then
11:35 anddam git remote show origin
11:35 IPXSam git@github.com
11:35 anddam as I mentioned earlier there's no protocol there
11:36 osse git will use ssh in that ase
11:36 osse case
11:36 anddam switch to the git protocol URL and it'll work as expected
11:36 zeroed joined #git
11:36 zeroed joined #git
11:36 osse but then he can't push
11:36 anddam osse: not in my case, with git@github.com I get prompted for a passphrase
11:36 osse exactly
11:36 IPXSam well when I switch to https etc then it asks for username and password
11:36 anddam that's why I came here asking my question in first place
11:36 IPXSam which is even more annoying
11:36 anddam ohhhh
11:36 anddam passphrase
11:36 anddam RSA passphrase, my bad
11:37 anddam I was prompted for username and password and thought you were having the same issue
11:37 IPXSam well do you not?
11:39 anddam I don't think, I'm asked for "username and password", you're asked for "passphrase"
11:40 osse username and passord is your github login. that's when you use http
11:41 osse passphrase is for the SSH key. naturally only when you use SSH
11:41 osse and only if your key has a passphrase in the first place
11:41 IPXSam This is so weird, because ssh-agent is running but whatever I do, adding the RSA changes nothing when it comes to a commit I always get asked for the passphrase
11:41 IPXSam If I find no fix I'll just remove the passphrase lol
11:41 IPXSam But there should be a *sane* way to do this
11:42 osse There probably is. But it's out of Git's hands
11:43 IPXSam Someone in this channel must know how though, #openssh is cold and dead
11:44 osse my guess: write a script that just prints the passphrase. then export SSH_ASKPASS=/path/to/script; export GIT_SSH_COMMAND='ssh "$@" < /dev/null'
11:45 irco joined #git
11:45 thecha joined #git
11:46 thecha how can i make an automated git log message when i commit via bashcript?
11:46 thecha i added the date but it has been pointed out to me that this was utterly useless icne git commits already ship with a datetiem prepacked
11:48 Infiltrator joined #git
11:48 thecha nevermind... I'm just gonna google...
11:48 cbreak thecha: you can pass the message to commit
11:49 cbreak but properly generating a good commit message will likely require a high quality AI
11:49 cbreak certainly better than anything that exists these days
11:49 Infiltrator thecha: But if it is only temporary (is that still correct?) then the message does not really matter much.
11:50 blackwind_123 joined #git
11:50 thecha cbreak couldnt one use the git fucntion that allows to show the changes?
11:50 thecha and then take like the first line of that?
11:50 cbreak thecha: that sounds braindead
11:50 thecha i know it's crude but at least it shows some change
11:50 cbreak thecha: git can show you the diffs already
11:50 cbreak no point storing them in the commit message
11:51 thecha but dont you want your commit messages to tell you waht the commit was all about?
11:51 alhariel joined #git
11:51 cbreak thecha: the commit message should describe the reason of the commit, and a summary of the contents, in human readable form
11:51 thecha cbreak maybe i shold familiarize myself with git more
11:51 cbreak NOT something dumb like a diff
11:51 thecha i see
11:51 osse thecha: just answer the question: What does the commit do?
11:51 osse Explain it to me
11:51 thecha and getting such a ocmmit message means ai
11:51 osse Then write it down. then give that to git commit.
11:52 thecha and an ai that some one way smart would work on a while
11:52 thecha osse: yes
11:53 thecha cbreak well then i cannot have any good commit message if i need to interrupt my work... I will jsut make it out to say "got interrupted no idea what i was doing at the time"
11:53 thecha at least then i know it was a knee jerk commit
11:53 thecha thanks cbreak sorry for the bother
11:53 osse sounds like you're looking for git stash
11:54 thecha left #git
11:55 cbreak that sounds like you need to think more
11:56 cbreak if you don't know what you're wroking on RIGHT WHEN YOU GET INTERRUPTED...
11:56 cbreak then ... that's a problem
11:57 osse i think we wanted a quick script to run "save the state" or something
11:57 osse if he additionally doesn't want to type a message then AI is required
11:58 m0viefreak joined #git
11:59 Infiltrator Yeah, bu git stash.
12:00 Infiltrator /bu/but/
12:00 ArnoFrost joined #git
12:02 eivarv joined #git
12:03 cbreak if he wanted git stash, why not just use it?
12:05 psvo[m] joined #git
12:09 BSAlb joined #git
12:10 zeroed joined #git
12:10 zeroed joined #git
12:14 jstein_ joined #git
12:16 osse I suspect he wanted git stash for his situation
12:16 osse as for why not use it: he probably didn't (doesn't) know it exists
12:17 osse it was first when he wrote "got interrupted.." I realized what he was trying to do
12:17 ahmedelgabri joined #git
12:18 seishun joined #git
12:25 dviola joined #git
12:26 Flowinho joined #git
12:27 Siegfried joined #git
12:28 LucaTM joined #git
12:35 nikivi joined #git
12:36 Raging_Hog joined #git
12:38 seishun joined #git
12:38 aard_ joined #git
12:48 rorro joined #git
12:49 traxo-xx joined #git
12:54 GrandPa-G joined #git
12:54 alex1a joined #git
12:54 Dragonbird joined #git
12:55 GrandPa-G is there anyone who could help a semi-novice with a very specific problem?
12:56 bremner !ask
12:56 gitinfo Yes, it's okay to ask questions here.... in fact, you just asked one! ;-) Pretty much any question is fine. We're not terribly picky, but we might be asleep. Please be patient and you should get an answer soon.
12:59 tvw joined #git
13:01 GrandPa-G Situation: I have a headless machine (no one there, no keyboard, no monitor..) so I am trying to fix a problem that was created. This may not be possible.
13:01 cbreak doesn't sound like a problem that git can solve indeed
13:02 GrandPa-G Local windows machine has source of linux script file. Repro is on github. headless machine is linux based.
13:02 GrandPa-G All I want to do is to have the headless machine copy from github when there is an update via the windows machine. So the commands that
13:02 iLembus joined #git
13:03 GrandPa-G that are being use are (one per line) git reset --hard HEAD git pull --depth=1
13:04 GrandPa-G The problem is that when a change is maded on the windows machine and synched, the headless machine gets the update but with the
13:05 GrandPa-G <<<< >>>> merge differences lines which then can't be executed as a script file. I just want the file to be moved, don't care what it was before.
13:05 cbreak GrandPa-G: then don't merge
13:05 cbreak pull means merge
13:05 cbreak if you don't want to merge, don't tell git to merge
13:06 cbreak just fetch what you want, then reset
13:06 cbreak GrandPa-G: see also !deploy
13:06 gitinfo GrandPa-G: Git is not a deployment tool, but you can build one around it (in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/deploy.html
13:06 GrandPa-G I think I am a bit stuck since I can't change what is being done on the headless machine, correct?
13:07 cbreak why not?
13:07 GrandPa-G I will look at the deploy idea. Didn't know about it. I may just change to a ftp type approach.
13:08 GrandPa-G Pretend the headless machine is the mars rover. A bit hard to make changes. I really can, but the complexity of getting a new set of code
13:08 GrandPa-G on the headless is difficult.
13:08 aspiers joined #git
13:08 cbreak GrandPa-G: then make sure there will never be merges
13:09 cbreak ensure it is fast forward, always
13:09 GrandPa-G This is were my skill level is low. Can I, from the windows side, make sure there are never merges? or since I am doing a git pull I am screwed?
13:10 cdg joined #git
13:10 cbreak make sure that there are no commits on that headless machine that you do not also have
13:11 GrandPa-G there never have been any commits on the headless machine. No one there to change anything unless something got messed up.
13:11 jost joined #git
13:11 jaguarmagenta joined #git
13:11 cbreak GrandPa-G: there have been
13:11 cbreak otherwise it would not merge
13:11 cbreak this is a fact.
13:12 ljubak joined #git
13:13 GrandPa-G Since I can't get any changes there without the merge extra stuff in a script file, I think I need to start building my rocket to head to mars to make a repair!
13:16 zeroed joined #git
13:16 zeroed joined #git
13:17 basiclaser joined #git
13:18 panzergame joined #git
13:18 b100s joined #git
13:18 moei joined #git
13:21 sunri5e joined #git
13:23 xall joined #git
13:25 Phylock joined #git
13:25 panzergame Hello everyone, i'm trying to merge a patch using : git am -3 < patch. I got some conflicts i solved them and added the file modified and i run as git status said "git am --continue". But it's raising the error "Application de \n fatal: empty ident name (for <>) not allowed". Did someone have solution ?
13:26 PCatinean joined #git
13:26 pks joined #git
13:27 xaa joined #git
13:30 panzergame if i commit and do git am --abort i will not lost my index ?
13:33 panzergame my messages are visible ?
13:34 Gamecubic joined #git
13:35 panzergame left #git
13:36 aranea joined #git
13:38 ajpiano joined #git
13:38 cyan__ joined #git
13:38 cbreak they are.
13:39 aranea Hi. I'm trying to write a git alias that merges the branch sync/<current branch> into my current branch.
13:39 aranea I guess 'alias.ffs !git merge --ff-only sync/"$(git symbolic-ref --short HEAD)"' is the way to go?
13:39 aranea Or does anyone have a better idea?
13:40 CheckDavid joined #git
13:47 anuxivm joined #git
13:48 seishun joined #git
13:48 Vinnie_win_c joined #git
13:49 svm_invictvs joined #git
13:50 adac joined #git
13:52 j416 joined #git
13:54 stfn joined #git
13:54 hsg86 joined #git
13:56 xall joined #git
13:59 BSaboia joined #git
14:04 Darren_ joined #git
14:05 troulouliou_dev joined #git
14:08 dikiaap joined #git
14:09 lindenle joined #git
14:11 d0nn1e joined #git
14:12 hahuang65 joined #git
14:13 aard_ joined #git
14:15 ayjay_t joined #git
14:15 Noldorin joined #git
14:16 zivester joined #git
14:17 dar123 joined #git
14:22 adac joined #git
14:24 HoierM joined #git
14:25 aranea git only uses the subdirectories "heads", "remotes" and "tags" of .git/refs/, right?
14:25 aranea Is it acceptable to create other, custom dirs in .git/refs?
14:25 ok91 joined #git
14:26 sdothum joined #git
14:26 jaguarmagenta joined #git
14:27 dendazen joined #git
14:28 nwkj86 joined #git
14:29 Rodya_ joined #git
14:30 krillr joined #git
14:33 re1 joined #git
14:35 hhee joined #git
14:41 jknetl joined #git
14:43 osse aranea: yes it's acceptable. git filter-branch uses refs/original to store the backups, for example
14:44 osse git stash uses refs/stash
14:46 aranea Thanks! Any other names that should be avoided?
14:46 vdv joined #git
14:47 aranea To avoid conflicts, I've named my new dir "refs/mysync" instead of "refs/sync", that'll hopefully be safe.
14:48 osse not that i know pf
14:49 Siegfried joined #git
14:52 osse alias looks fine btw
14:52 aranea Okay, thanks.
14:53 aranea I originally had those "sync" branches in refs/heads/sync/ and pushed with the refspec refs/heads/*:refs/heads/sync/*; after a couple of round-trips that lead to branch names like sync/sync/sync/master :)
14:57 chris2 joined #git
14:58 zeroed joined #git
14:59 phos1 joined #git
15:00 osse i think you can specify more refspecs
15:00 osse i'm confused. are the local branches named foo and the remote branches named sync/foo ?
15:02 sea-gull_ joined #git
15:03 Learath2 joined #git
15:05 Lauven joined #git
15:06 aranea osse: Yes, exactly.
15:07 aranea The branch is named foo, but to avoid pushing to a branch which is currently checked out on the remote, I push to sync/foo.
15:07 aranea Or rather, refs/mysync/foo, to avoid the sync/sync/sync/sync/... issue I described.
15:11 Lauven joined #git
15:15 kuppi joined #git
15:15 systemovich joined #git
15:17 venmx joined #git
15:20 ahmed_elgabri joined #git
15:25 Discovery joined #git
15:26 anddam left #git
15:26 Gloomy joined #git
15:26 cdown joined #git
15:27 IlNominePatre joined #git
15:29 shiriru joined #git
15:32 maroloccio joined #git
15:32 dar123 joined #git
15:32 venmx joined #git
15:32 johnny56_ joined #git
15:35 psvo[m] left #git
15:39 sq-one joined #git
15:40 mkopriva joined #git
15:41 venmx joined #git
15:41 mkopriva left #git
15:46 cdg joined #git
15:47 saurus joined #git
15:50 eivarv joined #git
15:52 Oatmeal joined #git
15:56 dfaught joined #git
15:58 stefanct joined #git
15:58 stefanct git check-attr needs a "--names-only" switch
15:59 treehug88 joined #git
16:01 BSAlb joined #git
16:02 ahmedelgabri joined #git
16:02 kier joined #git
16:03 johnny56_ joined #git
16:04 ahmedelgabri joined #git
16:06 jaguarmagenta joined #git
16:07 endiruna joined #git
16:09 nowhere_man joined #git
16:10 seishun joined #git
16:10 heroux joined #git
16:11 ojdo joined #git
16:12 jaguarmagenta joined #git
16:14 GavinMagnus joined #git
16:16 Siegfried joined #git
16:16 dunpeal joined #git
16:16 dunpeal Hi. Is there a concept of "hidden branches" in Git?
16:16 dunpeal I have a bunch of "dormant" branches, that I may get back to at some point, but for now they're just cluttering my "git branch" display.
16:17 dunpeal I'd like to be able to filter them out from "git branch".
16:19 done joined #git
16:21 osse aranea: sounds like you want !deploy
16:21 gitinfo aranea: Git is not a deployment tool, but you can build one around it (in simple environments) or use it as an object store(for complex ones). Here are some options/ideas to get you started: http://gitolite.com/deploy.html
16:21 prg3 joined #git
16:22 ochorocho__ joined #git
16:23 aranea osse: Actually, not quite. I'm just syncing several working copies of a repo.
16:23 aranea (For which I don't have a central bare repo located on a server)
16:23 stefanct dunpeal, you can push it to some refs/ subdir !heads
16:23 aranea But don't worry about it, I've solved my problem.
16:27 cdown joined #git
16:28 Goplat joined #git
16:29 dunpeal stefanct: thanks
16:29 dunpeal Suppose I have a branch foo, and I do `git rebase master`. When I get conflicts, there's a "local" and "remote" state. Am I right that "local" would be master, and "remote" would be foo?
16:30 dunpeal I.E. "local" is the commit I'm rebasing onto, while "remote" is the commit I'm rebasing?
16:33 nfk joined #git
16:33 oskarkv joined #git
16:34 msonntag joined #git
16:35 rewt dunpeal, "local" would be "foo", the commit you are rebasing, and "remote" would be "master", the commit you're rebasing on
16:35 dunpeal rewt: what would HEAD be?
16:36 rewt HEAD is always the commit you have checked out
16:36 anonymuse joined #git
16:36 rewt well, and if you make commits to it, it advances to that commit
16:37 aax joined #git
16:38 lindenle joined #git
16:38 anuxivm left #git
16:38 dunpeal rewt: so if I'm rebasing multiple commits, HEAD would be my current state, and REMOTE wuld be the one I'm replaying?
16:39 dunpeal I guess I'm just not clear on what's LOCAL/REMOTE and HEAD vs whatever commit is in the name.
16:41 osse dunpeal: /17
16:41 osse ehh
16:41 osse disregard
16:42 chris2 joined #git
16:43 rewt hmm, i'm not sure what happens to HEAD in the middle of th rebase
16:44 osse rewt: you are mistaken. in a rebase when resolving conflicts, local is the branch being rebased onto, and remote is whatever commit won't apply
16:45 osse it's the other way around from what it is when you merge. it's annoying
16:45 madewokherd joined #git
16:46 rewt ah, yeah, that's right
16:47 A5101 joined #git
16:47 aranea dunpeal: Yes, osse is right (that is, your assumption was right). It makes some sense, too, if you think of a rebase as a series of cherry-picks or something like that.
16:50 osse aranea: that's exactly what it is
16:51 osse in the literal sense
16:51 osse LITERALLY
16:52 GavinMagnus left #git
16:54 aranea osse: Indeed? Well, turns out my mental model of rebase isn't all that bad then. :)
16:54 b100s joined #git
16:55 dunpeal One things that's confusing is that sometimes git uses the terms "LOCAL" vs "REMOTE", and other times "HEAD" vs "some other commit". Can I assume these are always equivalent, respectively?
16:56 cagmz joined #git
16:58 iLembus joined #git
16:59 Lauven joined #git
17:00 cyan__ joined #git
17:01 dreiss joined #git
17:02 LucaTM joined #git
17:02 jaguarmagenta joined #git
17:03 vuoto joined #git
17:08 anonymuse joined #git
17:10 osse when does it use HEAD vs some other commit ?
17:10 Sasazuka joined #git
17:11 grayjoc joined #git
17:11 alex1a_ joined #git
17:12 vuoto joined #git
17:12 Gloomy joined #git
17:12 sssilver joined #git
17:12 qws-user-1229 joined #git
17:14 xcesariox joined #git
17:15 jstein_ joined #git
17:16 xall joined #git
17:20 navidr joined #git
17:24 SwiftMatt joined #git
17:25 InfoTest joined #git
17:25 moestevens joined #git
17:26 dunpeal osse: in the annotation in conclicting files.
17:26 dunpeal >>>> HEAD
17:26 dunpeal <<<< Other Commit
17:28 JSharpe joined #git
17:36 aranea joined #git
17:36 cdg joined #git
17:38 topi` joined #git
17:38 prg3 joined #git
17:39 dfaught joined #git
17:39 quackgyver joined #git
17:42 osse I would guess HEAD is synonymous with LOCAL
17:42 Domhack joined #git
17:47 vuoto joined #git
17:48 Sasazuka joined #git
17:48 nicksloan joined #git
17:52 [cust] joined #git
17:54 vuoto joined #git
17:54 vuoto joined #git
17:57 infernix joined #git
17:58 sanityflux joined #git
17:58 vuoto joined #git
17:59 inflames joined #git
18:03 Starky joined #git
18:06 ych joined #git
18:06 vuoto joined #git
18:07 malwar3hun73r joined #git
18:08 malwar3hun73r left #git
18:08 eivarv joined #git
18:09 b100s left #git
18:10 Starky joined #git
18:11 inflames joined #git
18:15 LucaTM joined #git
18:16 cagedwisdom joined #git
18:22 Rickmasta joined #git
18:24 Vangelis joined #git
18:24 Mixologic joined #git
18:27 svm_invictvs joined #git
18:31 therealGent joined #git
18:35 prg3 joined #git
18:39 finalbeta joined #git
18:39 HoierM joined #git
18:39 jfelchner joined #git
18:39 tobiasvl dunpeal: where does it use LOCAL and REMOTE though?
18:40 tobiasvl HEAD and "other commit" should be easy enough, you don't always merge in something from a remote
18:40 seishun joined #git
18:41 JamesBaxter joined #git
18:45 cdg joined #git
18:49 cdg joined #git
18:49 rewt tobiasvl, LOCAL and REMOTE are like "this commit" and "that commit" when merging/rebasing... it doesn't refer to local/remote repo
18:52 anonymuse joined #git
18:52 ljubak joined #git
18:53 tobiasvl ah
18:53 eivarv joined #git
18:53 tobiasvl yeah I recall that now
18:53 tobiasvl thought it was OURS and THEIRS
18:54 tobiasvl git uses a lot of different nomenclature here I guess
18:54 osse tobiasvl: temp names with git mergetool for example
18:54 phos1 joined #git
18:55 GT4066 joined #git
18:59 tobiasvl yeah
19:00 dunpeal Actually, that's a good question: how do "ours" and "theirs" fit into this picture?
19:05 InfoTest1 joined #git
19:07 Gloomy joined #git
19:07 xall joined #git
19:15 astrofog joined #git
19:23 davimore joined #git
19:25 dikiaap joined #git
19:29 skunkz joined #git
19:29 mmlb joined #git
19:29 v-y joined #git
19:30 Rodya_ joined #git
19:32 jaguarmagenta joined #git
19:35 adac joined #git
19:37 robotroll joined #git
19:39 ayjay_t joined #git
19:40 stux|RC-only joined #git
19:43 Infiltrator joined #git
19:45 ahmedelgabri joined #git
19:47 frobnic joined #git
19:47 multi_io joined #git
19:48 Infiltrator_reco joined #git
19:53 Lyqyd joined #git
19:54 cdown joined #git
19:56 govg joined #git
20:00 aard_ joined #git
20:01 vuoto joined #git
20:04 m1dnight2 joined #git
20:07 ych joined #git
20:08 vdv joined #git
20:10 sssilver joined #git
20:11 jantje joined #git
20:11 rafasc joined #git
20:12 ericsupreme joined #git
20:12 rafasc Is there a way to use git add -p for the first file? I want to add some portion of my code but not all.
20:12 ericsupreme joined #git
20:13 tobiasvl the first file? what?
20:13 tobiasvl just do "git add -p -- file" ?
20:14 _ADN_ joined #git
20:14 rafasc that returns no changes cause I never added this file before.
20:18 finalbeta joined #git
20:19 jon-mac joined #git
20:21 Lea2 joined #git
20:22 Gloomy joined #git
20:22 rafasc running git add -N first solved it.
20:22 rafasc thanks
20:22 sanityflux left #git
20:23 dviola joined #git
20:24 EmeraldExplorer joined #git
20:30 muahah joined #git
20:30 muahah \part
20:30 muahah \part
20:31 tobiasvl /part
20:32 muahah thx...
20:32 muahah left #git
20:32 skift joined #git
20:33 vuoto joined #git
20:36 Seveas ⌿part
20:37 tnecniv joined #git
20:38 pothepanda joined #git
20:40 Infiltrator joined #git
20:40 robotroll joined #git
20:41 inflames joined #git
20:43 Gloomy joined #git
20:45 Vmsi joined #git
20:46 Gloomy joined #git
20:50 macivy joined #git
20:50 Gloomy joined #git
20:51 BigDawg joined #git
20:51 BDawg joined #git
20:51 nikivi joined #git
20:52 muahah joined #git
20:52 muahah left #git
20:55 nikivi joined #git
20:56 chris2 joined #git
20:56 t-mart joined #git
20:56 venmx joined #git
20:59 spacelord joined #git
20:59 spacelord joined #git
21:04 t-mart joined #git
21:05 spacelord joined #git
21:05 Doginal joined #git
21:06 oskarkv joined #git
21:06 spacelord joined #git
21:09 vuoto joined #git
21:15 thierryp joined #git
21:17 svm_invictvs joined #git
21:17 inflames joined #git
21:19 t-mart joined #git
21:24 Doginal_ joined #git
21:25 Rodya_ joined #git
21:29 seishun joined #git
21:29 llamapixel https://asciinema.org/   in case you want to write animated sequences of commands and you have the lesson creation bug ;)
21:33 jaguarmagenta joined #git
21:33 trondth joined #git
21:34 ResidentBiscuit joined #git
21:37 aidalgol joined #git
21:37 done joined #git
21:37 seishun joined #git
21:37 floatingman joined #git
21:39 davimore_ joined #git
21:40 paul424 joined #git
21:40 Infiltrator left #git
21:41 random-nick joined #git
21:41 random-nick is there a way to continue an interrupted git clone?
21:42 rewt what happens when you run it again
21:42 Seveas random-nick: no. an interrupted-git clone will simply wipe what it downloaded
21:42 random-nick ok
21:43 m0viefreak joined #git
21:43 rewt you can do a shallow clone (`git clone --depth=1`), and then increment that 1 to fetch more and more of the repo, and `git fetch --unshallow` to get it all
21:44 Oatmeal joined #git
21:44 rafasc left #git
21:45 rewt err, s/clone/fetch/ for the 'more and more' part
21:45 seishun joined #git
21:46 Brando753-o_O_o joined #git
21:50 cdg joined #git
21:52 josefig joined #git
21:54 oskarkv joined #git
21:59 netj joined #git
22:05 dunpeal joined #git
22:08 dunpeal Hi. I have a branch foo that was branched off master a long time ago. Since then, there were many commits made to it, and obviously even more made to master. What's the best strategy to merge foo into master?
22:09 cbreak dunpeal: git merge foo
22:09 dunpeal cbreak: rebasing foo onto master would be less efficient, right?
22:12 dunpeal Looks like it would be.
22:13 dunpeal I'm getting a lot more conflict, probably because the rebase is a series of cherry-picks, whereas a merge just reconciles the final diffs.
22:13 nikivi joined #git
22:14 snthsnth joined #git
22:14 oskarkv_ joined #git
22:18 Seveas dunpeal: that's correct
22:19 dunpeal Seveas: so what would you do if you really wanted to rebase in this situation?  Squash all the divergent commits on foo, then rebase the single squashed commit onto master?
22:19 Seveas I'd have rebased more often to begin with
22:19 dunpeal Guess that's the only way to avoid dealing with the conflicts induced by each individual commit.
22:20 Seveas which can be emulated by progressively rebasing forward in time. So first rebase foo onto let's say 10 commits ahead of the fork point, then 20 etc...
22:20 Seveas the merge conflicts will be smaller
22:20 dunpeal Well, sure, minimizing divergence by constant merging/rebasing is a good strategy, but too late for that now :)
22:21 dunpeal Seveas: hm, are you sure that will save time?
22:21 Seveas no
22:21 bmahe joined #git
22:21 Seveas depends on the situation
22:21 dunpeal I thought the extra work is because every time we rebase, we have to resolve each of the intermediate commit conflicts
22:21 Seveas but each conflict itself only once, as we keep rebasing ahead in time
22:22 Defcronyke hi
22:23 Seveas \o
22:23 raijin joined #git
22:24 vktec joined #git
22:25 Rodya_ joined #git
22:26 _ADN_ joined #git
22:26 SwiftMatt joined #git
22:27 Defcronyke hi Seveas
22:28 cagedwisdom joined #git
22:30 vktec joined #git
22:33 paul424 joined #git
22:40 pks joined #git
22:45 boombatower joined #git
22:47 Murii joined #git
22:48 ochorocho__ joined #git
22:49 anonymuse joined #git
22:49 dreiss joined #git
22:53 brent__ joined #git
22:53 pizzaops joined #git
22:59 cool_boy joined #git
23:00 cool_boy hi
23:00 cool_boy Please, commit your changes or stash them before you can switch branches.
23:00 cool_boy Aborting
23:00 cool_boy what can I do when I see above message? I do not want to commit on current branch also do not want to discard them
23:00 osse cool_boy: stash
23:00 osse man git-stash
23:00 gitinfo the git-stash manpage is available at http://jk.gs/git-stash.html
23:01 cool_boy osse: thanks will read it
23:01 finalbeta joined #git
23:02 truedichotomy joined #git
23:05 Masber joined #git
23:06 w0ng joined #git
23:06 w0ng left #git
23:08 pflanze I can't find any documentation on the "encoding" header in commits.
23:09 pflanze I've noticed that when I run filter-branch over the history of one of my projects, it removes the "encoding latin1" header from commits which causes them to get different ids even though everything else stays the same.
23:10 pflanze I was using an editor that uses latin1 to edit commit messages in the past, but oddly thought I never set up git for that. Also oddly, git config -l doesn't show anything regards encoding.
23:10 pflanze So I'd be happy to simply drop the encoding header in commits from now on, but how do I do that when it's not in git config?
23:11 cool_boy osse: thanks it was what I needed, just one more question stash thing always remains in local only? we can or can't push them to remote?
23:12 vktec cool_boy: No, you can't push stashes
23:12 cool_boy vktec: thanks
23:13 svm_invictvs joined #git
23:14 vdv joined #git
23:15 JanC_ joined #git
23:15 pbrewczynski joined #git
23:18 Sasazuka joined #git
23:19 Seveas sure you can push stashes. Whether you should is a different question (to which the answer would be: "hell no")
23:20 Celelibi Is there a git front end for hg repositories? :)
23:20 vktec Seveas: Oh, you can? I didn't know that
23:20 vktec Celelibi: What's wrong with using hg?
23:20 Celelibi I just don't know how to use it.
23:20 vktec It's not _that_ much different from git, iirc
23:20 ResidentBiscuit joined #git
23:21 vktec Probably not too hard to learn
23:24 anonymuse joined #git
23:28 Seveas Celelibi: install git-cinnabar and use git clone hg::url-of-hg-repo
23:28 Celelibi I found git-remote-hg
23:28 anonymus_ joined #git
23:29 kaldoran joined #git
23:32 SwiftMatt joined #git
23:33 frostythesnowman joined #git
23:34 jaguarmagenta joined #git
23:40 Mobutils joined #git
23:42 Rodya_ joined #git
23:43 llamapixel omg https://github.com/stevenjack/cig
23:43 Rickmasta joined #git
23:43 Masber joined #git
23:46 chris2 joined #git
23:47 bmahe joined #git
23:49 cdg joined #git
23:50 Mobutils joined #git
23:52 neunon joined #git
23:58 dikiaap joined #git

| Channels | #git index | Today | | Search | Google Search | Plain-Text | summary