Perl 6 - the future is here, just unevenly distributed

IRC log for #git, 2017-01-14

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

All times shown according to UTC.

Time Nick Message
00:00 thebope joined #git
00:03 boutcher joined #git
00:04 chosafine joined #git
00:05 UserOO7 joined #git
00:05 safe joined #git
00:05 justanotheruser joined #git
00:05 hbtxewknhkzymctj joined #git
00:10 anonymuse joined #git
00:16 pietv joined #git
00:18 chipotle joined #git
00:19 jimi_ joined #git
00:20 ColdKeyboard[a] joined #git
00:20 madewokherd joined #git
00:22 morenoh149 joined #git
00:22 morenoh149 how do I undo the latest commit with another commit?
00:22 morenoh149 an undo commit
00:23 shgysk8zer0 joined #git
00:24 imachuchu morenoh149: look into the revert command
00:25 jimi_ joined #git
00:25 acetakwas joined #git
00:25 jimi_ joined #git
00:26 zivester joined #git
00:29 drizbit joined #git
00:31 morenoh149 imachuchu: and then how do I replay a commit?
00:32 morenoh149 git cherry-pick
00:33 jccn joined #git
00:33 str joined #git
00:34 drizbit joined #git
00:41 Sasazuka joined #git
00:42 xaviergmail joined #git
00:42 mischat joined #git
00:44 Darren_ joined #git
00:46 erebel55 joined #git
00:47 brandonw joined #git
00:49 nidr0x joined #git
00:50 axisys joined #git
00:52 pietv joined #git
00:57 str joined #git
00:57 arescorpio joined #git
00:58 kyan joined #git
00:58 stick-shift joined #git
00:59 chipotle joined #git
01:02 jarshvor joined #git
01:05 timvisher joined #git
01:08 done joined #git
01:11 snits joined #git
01:13 de-vri-es joined #git
01:15 ljubak joined #git
01:15 pietv joined #git
01:18 j0y joined #git
01:19 Sasazuka joined #git
01:20 silentz0r joined #git
01:21 silentz0r hello. I have two git repositories and would like to merge them into one, maintaining both repo's history (i.e. merge files and history as well). The two repos do not share any files, in fact they both have one or two base directories with different names. Is this possible in a neat manner?
01:23 Kaisyu joined #git
01:23 Electrometro joined #git
01:28 shinnya joined #git
01:30 MattMaker joined #git
01:31 slayerjain joined #git
01:32 grill joined #git
01:33 brent__ joined #git
01:34 netj joined #git
01:35 thiago joined #git
01:35 mikhael_k33hl joined #git
01:36 mikhael_k33hl I've committed and pushed twice to the branch. How do I remove the first commit/pushed changes?
01:40 hahuang61 joined #git
01:44 dnakuru joined #git
01:50 silentz0r followup, basically I want to "merge" all the changes from repo B into my repo A. There are no conflicts between the two repos as they don't share common files.
01:51 MattMaker joined #git
01:53 MattMaker joined #git
01:57 mattmaker joined #git
01:57 jarshvor joined #git
01:57 garethdaine left #git
01:58 nettoweb joined #git
02:00 kier left #git
02:02 dnakuru left #git
02:03 stick-sh_ joined #git
02:06 MattMaker joined #git
02:08 dsantiago joined #git
02:08 nowhere_man joined #git
02:09 mizu_no_oto joined #git
02:12 rizonz I have some weird conflict when I want to merge my change, I wonder why it can conflict... ther eis only some enters which are changed
02:12 raspado joined #git
02:15 SantaClauze joined #git
02:16 rizonz rawtaz: ?
02:18 Electrometro joined #git
02:25 re1_ joined #git
02:25 finalbeta joined #git
02:26 pks joined #git
02:29 dreiss joined #git
02:31 griffind_ joined #git
02:34 ph88_ joined #git
02:37 flavi0_ joined #git
02:40 d^sh joined #git
02:48 ilbot3 joined #git
02:48 Topic for #git is now Welcome to #git, the place for git help and a fresh start on a new branch | Public logs at http://jk.gs/glog | First visit? Read: http://jk.gs/git | Current stable version: 2.11.0 | Getting "cannot send to channel"? /msg gitinfo .voice | This channel may contain users known to the state of California to cause cancer.
02:50 Vampire0 joined #git
02:52 umpc joined #git
02:59 xissburg_ joined #git
02:59 xissburg_ you can't undo git reset --hard @HEAD{1} right?
02:59 xissburg_ *HEAD@{1}
02:59 a_thakur joined #git
02:59 xissburg_ ok I think I lost some code :3
03:00 a_thakur joined #git
03:00 b3kN joined #git
03:00 b3kN joined #git
03:01 a_thakur joined #git
03:01 albel727 joined #git
03:01 aidalgol joined #git
03:01 a_thakur joined #git
03:02 a_thakur joined #git
03:04 a_thakur joined #git
03:05 lalilulelo joined #git
03:05 Dredd xissburg_, git reflog
03:05 ome joined #git
03:06 xissburg_ nah, uncommited changes
03:06 xissburg_ those can't be recovered
03:06 Dredd ah
03:06 xissburg_ fuck git ;)
03:06 * Dredd pets Git
03:06 Dredd Git ate your homework?
03:07 xissburg_ yeah I'll call it a day
03:08 exounx joined #git
03:09 jagob joined #git
03:11 jimi_ joined #git
03:14 chachasmooth joined #git
03:15 grilled-cheese howdy all
03:16 grilled-cheese So I'm working on converting a terrible long lived mercurial forked repo into a git branch
03:17 grilled-cheese I've got a git commit with all the changes finally from patching fun
03:17 grilled-cheese I'm trying to clean it up though
03:18 grilled-cheese At some point some brilliant person ran conversion script and is going to make whomever gets this pull request a nightmare
03:18 rizonz heh you can make a mess out of your git timeline :P
03:19 grilled-cheese I'd like to determine if there's a way to basically run a patch generation and ignore certain types of text changes
03:19 grilled-cheese for example changing single and double quotes in an xml file
03:20 grilled-cheese or single quotes to &
03:21 hexagoxel joined #git
03:21 thiago joined #git
03:22 grilled-cheese rizonz, a now former collegue of mine did serious wizardry to stitch 4 different source control systems and a total of 7 different repositories back together to restore around 13 years of history in a single git repo
03:23 grilled-cheese I'm left with migrating all the feature branches over from whereever they might be hiding
03:24 grilled-cheese git diff and format-patch do give you some flexibility in terms of whitespace
03:24 rizonz grilled-cheese: wow!
03:24 rizonz I use gitlab and am very happy with it but I'm new to it
03:24 rizonz so from time to time I need need to close a merge request or so
03:24 grilled-cheese we just moved to VSTS
03:24 Vortex35 joined #git
03:25 rizonz grilled-cheese: ah! now I remember your name
03:25 grilled-cheese :)
03:25 rizonz yeah I moved away from subversion
03:25 rizonz svn is great tho
03:25 rizonz git is nicer
03:25 rizonz but SVN is good
03:25 rizonz very good to start with
03:25 grilled-cheese it's one of the better central source backends out there
03:26 rizonz svn ?
03:26 grilled-cheese yes
03:26 grilled-cheese I like git a lot better
03:26 grilled-cheese our devs are starting to use it and enjoying it
03:26 grilled-cheese myself included
03:27 rizonz yap me too
03:27 rizonz but SVN is rocksolid
03:27 rizonz if you ask me
03:27 grilled-cheese although I've been using it for some time in OSS projects independently
03:27 llamapixel git is king
03:27 rizonz I never shamed myself of using it but I never wanted to follow the fancy boys
03:27 grilled-cheese in 2011 we bet on the wrong horse with mercurial
03:27 rizonz oh
03:27 le_melomane joined #git
03:28 llamapixel i convert my binary to hex before lfs and this solves massive crazy artist psd files
03:28 llamapixel evil grin
03:28 rizonz I needed to understand upstream a little bit more, it's simple but GitLab does a GREAT! job
03:28 thiago it doesn't make your repository any smaller
03:28 llamapixel the size pays off after 4 commit changes
03:29 grilled-cheese we're a windows software shop, so VSTS is "free" for us because we have to pay the windows OS tax
03:29 thiago it shouldn't
03:29 rizonz llamapixel: you have psd's in git ?
03:29 grilled-cheese llamapixel, I hadn't considered this
03:29 grilled-cheese that's rather clever
03:29 thiago if the file changes enough, then the compressible hex isn't any more delta'able than the binary
03:29 llamapixel i can now by making them a text based ascci file for storage with lfs
03:30 kevleyski joined #git
03:31 grilled-cheese my predecessor really didn't like git-lfs because it doesn't always interoperate and goes against the distributed nature of git
03:32 Goplat joined #git
03:32 grilled-cheese our new git repo is around 24G after we slimmed it down by dropping ancient binaries in the history
03:32 grilled-cheese roughly 8.5M lines of source :\
03:35 arescorpio joined #git
03:35 sunri5e joined #git
03:35 grilled-cheese so is anyone aware of a method or tool to perform some more intimate patch file creation/application
03:35 llamapixel rizonz:  yeah social media gamedev
03:35 unbalanced joined #git
03:35 llamapixel you just rate your artists ocd level and assign them a dedicated repo or hex their work before you commit and unhex it to use it.
03:36 llamapixel i have two continuos repos i keep testing to make sure it works, so far so good.
03:36 llamapixel one thing I have been doing is replacing large pixel array media with text baswd shaders and 3d models in ascii format fbx
03:38 llamapixel at some stage the (n) resolution of media for sd/hd /uhd and upwards wont be workable due to the amount of media you have to push through
03:40 hahuang61 joined #git
03:40 snowkidind joined #git
03:48 fstd_ joined #git
03:49 ertes joined #git
03:49 jarshvor joined #git
03:55 raspado joined #git
03:56 drbean joined #git
03:56 rivarun joined #git
04:00 raspado joined #git
04:02 morsecat joined #git
04:02 tjk joined #git
04:03 rkazak joined #git
04:03 ReptilianBrain joined #git
04:14 d1z joined #git
04:15 jason237 joined #git
04:15 chipotl__ joined #git
04:22 gfixler joined #git
04:22 inflames joined #git
04:22 syg_ joined #git
04:33 jimi_sanchez joined #git
04:33 Nilesh_ joined #git
04:36 ph88^ joined #git
04:40 rchavik joined #git
04:43 duderonomy joined #git
04:46 stoopkid joined #git
04:47 stoopkid are there any standards documents/organizations laying out standards for revision control processes?
04:48 nivag joined #git
04:52 romerocesar joined #git
04:53 rivarun joined #git
04:55 jimi_ joined #git
04:56 grilled-cheese not sure I follow
04:57 grilled-cheese gitflow is a fairly standard practice in some realms for managing how code moves in a repo
04:58 phroa stoopkid: man gitworkflows
04:58 gitinfo stoopkid: the gitworkflows manpage is available at http://jk.gs/gitworkflows.html
04:58 phroa !book
04:58 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
04:59 stoopkid i mean like ISO / IEC / W3C / etc.. standards
05:00 phroa oof
05:01 thiago i can say with almost certainty that there aren't any that involve Git
05:01 thiago therefore, not relevant to this channel
05:02 phroa I found a National Institute of Dental and Craniofacial Research (it's a .gov!) document describing how to number revisions in the headers of Word documents
05:02 phroa which they call "version control"
05:02 thiago there are probably standards that are tangentially relevant, going even to things like financial regulation requiring documentation to be kept
05:04 phroa I think your best bet would be trying to find something describing NASA's git usage protocols, though I agree with the above.
05:07 thiago joined #git
05:12 fahadash joined #git
05:13 AlexMax joined #git
05:13 AlexMax I did a revert that I never committed
05:13 danslo joined #git
05:13 AlexMax I now no longer want to revert
05:13 AlexMax how do I get git to not pre-populate the commit message with "Reverted XYZ"
05:14 AlexMax I'm worried that I might be setting some "this dude reverted a commit on this commit" invisible metadata
05:15 AlexMax like
05:16 netj joined #git
05:16 jimi_sanchez joined #git
05:19 LordRyan joined #git
05:21 phroa AlexMax: there's really no metadata.  you can either change the message now with a commit --amend or an interactive rebase, or see man git-revert for the option to edit the message
05:21 gitinfo AlexMax: the git-revert manpage is available at http://jk.gs/git-revert.html
05:21 phroa (I might note that the default behaviour for revert is to let you edit the message before you actually do the revert...)
05:25 gautamsomani joined #git
05:25 svm_invictvs joined #git
05:31 howdoi joined #git
05:33 akkad joined #git
05:34 jellycode joined #git
05:34 ph88_ joined #git
05:39 Gloomy joined #git
05:42 Cabanossi joined #git
05:43 hahuang61 joined #git
05:43 mand0 joined #git
05:44 chosafine joined #git
05:44 chosafine left #git
05:46 jellycode Hi All, I want to write a web application which checks in with GIT repositories every so often, and scans the contents of any new commits.  Since it's a web application, I don't want to clone the whole repository to disk, which is the overall use case for git.  I just want to download the contents of specific commits by ID, then discard it.  I think I want something like a "patch" if it were possible,  but I'm no expert on GIT. I
05:46 jellycode also have found references that "single-commit-downloads" might be possible using newer features of "git-upload-pack" and "git-fetch-pack". However, I find the documentation to be beyond me at this time. Can anyone tell me if it's possible, and perhaps the command to do this?
05:48 subhojit777 joined #git
05:50 timvisher joined #git
05:50 akkad joined #git
05:51 mischat joined #git
05:53 syg_ joined #git
05:53 inflames joined #git
05:56 raspado joined #git
05:59 Abhijit joined #git
05:59 Abhijit hi
06:00 Abhijit I am writing a non English Ebook. Whats the industry standard recommendation for writing commits in Non English language? OR shall I keep commit messages in English only?
06:01 romerocesar_ joined #git
06:02 cyan__ joined #git
06:06 Anthaas joined #git
06:11 gugah joined #git
06:17 bocaneri joined #git
06:20 gautamsomani joined #git
06:21 Nitesh joined #git
06:21 manithree joined #git
06:22 menip joined #git
06:24 manithree left #git
06:27 finalbeta joined #git
06:31 shgysk8zer0 joined #git
06:31 rkazak joined #git
06:33 Peuc joined #git
06:39 pietv joined #git
06:39 rgrinberg joined #git
06:40 gautamsomani joined #git
06:42 notquitebrian joined #git
06:43 LordRyan joined #git
06:43 joco42 joined #git
06:45 rchavik joined #git
06:46 d1z joined #git
06:51 Wulf joined #git
06:53 thiago joined #git
07:00 dermoth joined #git
07:00 SwiftMatt joined #git
07:03 LordRyan joined #git
07:06 Peuc joined #git
07:07 cafuser0l joined #git
07:07 rkazak joined #git
07:12 gambl0re joined #git
07:15 youser joined #git
07:17 ShapeShifter499 joined #git
07:21 navidr joined #git
07:22 shgysk8zer0 joined #git
07:24 moritz Abhijit: that's like entirely your choice
07:26 gautamsomani joined #git
07:29 kadoban I'd hope that if you write your commits in utf-8 or something standard that'd work well just about everywhere, I'm not sure if commit messages and such actually have a defined encoding though.
07:32 overlord_tm joined #git
07:33 vuoto joined #git
07:34 gautamsomani joined #git
07:39 mehola joined #git
07:40 gusnan joined #git
07:42 dreiss joined #git
07:44 hahuang61 joined #git
07:44 shinnya joined #git
07:50 moei joined #git
07:51 youser joined #git
07:52 GuestTri joined #git
07:54 GuestTri joined #git
07:54 gautamsomani joined #git
07:55 theoceaniscool joined #git
07:56 GuestTri joined #git
07:56 rchavik joined #git
07:56 youser joined #git
07:57 GuestTri joined #git
07:58 gautamsomani1 joined #git
07:59 Ploppz joined #git
08:00 Ploppz https://bpaste.net/show/7e26c4ab52a7 why is HEAD 'detached'? I think what I did was to check out some earlier commit, do a small change to see if it worked, then `git reset --hard` to discard the changes, then checkout the latest commit again
08:02 PioneerAxon joined #git
08:04 kadoban Ploppz: Not really clear from the paste, we'd have to see what you actually did. You're in a detached HEAD because you don't have a branch checked out though, that's essentially the definition, not being on a branch.
08:04 kadoban So ... checkout a branch?
08:05 Ploppz but can I move the master to HEAD?
08:05 Oebele joined #git
08:06 kadoban If you want. That usually implies changing history, which if you've shared that history is not a good idea.
08:07 jagob joined #git
08:07 Ploppz what do I do with my latest commit then? can I merge it in to master?
08:08 kadoban Totally lost as to what you're trying to accomplish, or did already.
08:08 maret joined #git
08:09 Derperperd joined #git
08:09 Ploppz I was working on master when I committed branch ce776 and for some reason it's detached from master. I thought I was working on master
08:09 gautamsomani joined #git
08:09 Ploppz anyway, when I checked out master, my HEAD is still detached
08:10 milki Ploppz: !reattach
08:10 gitinfo Ploppz: Letters refer to !detached. (a) and (b): 'git checkout branchname' to continue working on another branch, or 'git checkout -b branchname' to start a new one here; (c) git am --continue; (d) git rebase --continue
08:10 kadoban !transcript
08:10 gitinfo Please paste (using https://gist.github.com/ or similar) a transcript ( https://git.io/viMGr ) of your terminal session so we can see exactly what you see
08:11 Ploppz ah, I tried to checkout the specific commit. I think it's fixed now. thanks
08:12 Abhijit joined #git
08:13 mehola joined #git
08:14 phanimahesh joined #git
08:14 Abhijit moritz, kadoban ok. thanks.
08:16 gautamsomani1 joined #git
08:16 gautamsomani joined #git
08:17 kadoban Abhijit: https://git-scm.com/docs/git-commit-tree has some info about commit message encodings, and other stuff, if you're interested.
08:18 spacelord_ joined #git
08:18 kadoban It sounds like it's at least a strong convention that commit messages are in utf-8 unless you go out of your way to tell it otherwise, and when you do, it records the encoding with the thing ... so should work great really.
08:18 subhojit777 joined #git
08:20 gambl0re joined #git
08:21 Abhijit ok
08:28 Murii joined #git
08:28 ankit01ojha joined #git
08:32 theoceaniscool joined #git
08:32 mjuszczak joined #git
08:33 Sasazuka joined #git
08:34 duderonomy joined #git
08:36 dsdeiz joined #git
08:36 dsdeiz joined #git
08:42 maret joined #git
08:42 thiago joined #git
08:57 maret joined #git
08:59 maret joined #git
09:03 cdown joined #git
09:08 jagob joined #git
09:13 nick123 joined #git
09:13 dimi1947 joined #git
09:22 armyriad joined #git
09:24 lindenle joined #git
09:27 ProbabilityMoon joined #git
09:27 zeroed joined #git
09:27 zeroed joined #git
09:28 timvisher joined #git
09:28 maret_ joined #git
09:28 nivag joined #git
09:29 danslo joined #git
09:31 maret joined #git
09:33 flavi0_ left #git
09:37 minikN joined #git
09:42 TFrag joined #git
09:44 hahuang61 joined #git
09:48 dersand joined #git
09:54 hhee2 joined #git
09:55 thierryp joined #git
09:55 marchelly joined #git
09:56 jimmyeatworld joined #git
09:57 robotroll joined #git
09:58 nowhere_man joined #git
10:00 absinthe joined #git
10:01 ramsub07 joined #git
10:06 nostrora joined #git
10:07 finalbeta joined #git
10:07 SpeakerToMeat joined #git
10:07 nettoweb joined #git
10:09 ramsub07 hi, i want to ignore all the changes being made to a file. I add that to .gitignore. The changes made to .gitignore also shows up on github :|
10:12 moritz ramsub07: !ignore_tracked
10:12 gitinfo ramsub07: Git only applies ignore patterns to untracked files. You can't use ignore patterns to ignore changes to files that are already tracked by git. To remove files only from git, but keeping them on disk, use git rm --cached <file>. Still, see https://gist.github.com/1423106 for ways people have worked around the problem.
10:13 afuentes joined #git
10:18 vdv joined #git
10:21 timvisher joined #git
10:23 pks joined #git
10:27 thiago joined #git
10:28 TomyLobo joined #git
10:31 mehola joined #git
10:34 t0by joined #git
10:34 t0by joined #git
10:34 zeroed joined #git
10:34 zeroed joined #git
10:37 eizua joined #git
10:40 Balliad joined #git
10:48 gautamsomani joined #git
10:50 pks joined #git
10:51 cyan__ joined #git
10:53 Gloomy joined #git
10:54 xkr47 joined #git
10:56 iLembus joined #git
10:58 mischat joined #git
11:01 timvisher joined #git
11:02 pijiu joined #git
11:11 silnp joined #git
11:11 Tobbi joined #git
11:13 rivarun joined #git
11:16 dhollinger joined #git
11:17 JrCs joined #git
11:23 gingitsune joined #git
11:24 gingitsune I have a >1gb text file commited in my repo. Can i rip it out some other way other than creating a new repo?
11:26 wendelmineiro joined #git
11:26 jast what do you mean, "rip out"?
11:30 t-mart_ joined #git
11:30 PHPanos joined #git
11:32 mehola joined #git
11:33 gingitsune jast: I want the repo not take up 1gb hard drive space for no good reason
11:34 gingitsune sadly i commited the file to the repo quite a while ago
11:37 youser joined #git
11:37 jnavila joined #git
11:38 iLembus joined #git
11:40 jast gingitsune: the only way to make that happen is to rewrite all the history starting from where the file was introduced. you can do it without cloning (using filter-branch), but all existing clones must be reset manually (or re-created)
11:40 osse !bfg
11:40 gitinfo A tool designed to remove large files, or passwords from history: https://rtyley.github.io/bfg-repo-cleaner/ (!rewrite applies)
11:40 jast right, bfg is a third-party tool to achieve this specifically. same caveats.
11:43 donught joined #git
11:43 joki joined #git
11:43 donught joined #git
11:45 hahuang61 joined #git
11:46 gingitsune thanks
11:48 _rht joined #git
11:50 nostrora joined #git
11:52 ertesx joined #git
11:52 leeN joined #git
11:55 satifant joined #git
11:58 raspado joined #git
12:00 absinthe joined #git
12:01 phanimahesh joined #git
12:05 Debyte joined #git
12:07 realtime joined #git
12:08 thiago joined #git
12:10 realtime_ joined #git
12:11 iLembus_ joined #git
12:12 King_Hual joined #git
12:13 str joined #git
12:13 glnz joined #git
12:17 m0viefreak joined #git
12:20 pks joined #git
12:22 ProbabilityMoon joined #git
12:29 mischat joined #git
12:31 jnavila joined #git
12:38 zeroed joined #git
12:41 rivarun joined #git
12:42 rivarun joined #git
12:43 nettoweb1 joined #git
12:46 miczac joined #git
12:47 Anja joined #git
12:51 Kaisyu joined #git
12:57 dodobrain joined #git
12:57 ojdo joined #git
12:58 absinthe joined #git
13:01 miczac_ joined #git
13:02 timvisher joined #git
13:03 jnavila joined #git
13:03 Balliad joined #git
13:05 manuelschneid3r joined #git
13:06 vuoto joined #git
13:11 Derperperd joined #git
13:12 zeroed joined #git
13:12 zeroed joined #git
13:12 phanimahesh joined #git
13:14 mlvd joined #git
13:15 bluepixel joined #git
13:18 miczac_ joined #git
13:18 thierryp joined #git
13:20 miczac_ joined #git
13:22 nowhere_man joined #git
13:22 ayogi joined #git
13:24 nowhereman joined #git
13:25 dersand joined #git
13:27 lindenle joined #git
13:27 miczac_ joined #git
13:30 AndChat216489 joined #git
13:31 mischat joined #git
13:32 miczac_ joined #git
13:34 sdothum joined #git
13:35 miczac_ joined #git
13:35 jameser joined #git
13:39 BSAlb joined #git
13:39 gambl0re joined #git
13:40 trinakria joined #git
13:42 borkr joined #git
13:44 iLembus__ joined #git
13:44 trinakria joined #git
13:46 hahuang61 joined #git
13:47 denisMone joined #git
13:49 miczac_ joined #git
13:50 thiago joined #git
13:51 re1 joined #git
13:51 CheckDavid joined #git
13:54 rorro joined #git
13:56 publio joined #git
13:56 mikecmpbll joined #git
13:58 nickabbey joined #git
14:01 realtime joined #git
14:01 gautamsomani joined #git
14:05 Derperperd joined #git
14:12 absinthe joined #git
14:14 shinnya joined #git
14:14 bill99 joined #git
14:15 chandu20 joined #git
14:16 jameser joined #git
14:18 zeroed joined #git
14:21 dodobrain joined #git
14:22 tjk joined #git
14:23 jozwior joined #git
14:24 Oqgf joined #git
14:27 ShekharReddy joined #git
14:28 mentazoom joined #git
14:32 zivester joined #git
14:32 mischat joined #git
14:34 vuoto joined #git
14:36 Balliad joined #git
14:36 netj joined #git
14:40 str joined #git
14:41 rivarun joined #git
14:41 borkr joined #git
14:45 afuentes joined #git
14:47 subhojit777 joined #git
14:48 uebera|| joined #git
14:49 uebera|| joined #git
14:51 multi_io_ left #git
14:53 tjk joined #git
14:55 codemann joined #git
14:56 gambl0re joined #git
14:59 Gloomy joined #git
15:01 vuoto joined #git
15:02 ramsub07 joined #git
15:04 Guest54781 joined #git
15:05 nwkj86 joined #git
15:06 Derperperd joined #git
15:07 nwkj86 joined #git
15:10 Khisanth joined #git
15:10 miczac_ joined #git
15:12 malt3 joined #git
15:13 AndChat216489 joined #git
15:14 phanimahesh joined #git
15:15 ramsub07 joined #git
15:18 hasc joined #git
15:18 ianmethyst joined #git
15:27 phtv joined #git
15:27 Balliad joined #git
15:28 chachasmooth joined #git
15:31 aard_ joined #git
15:33 PCatinean joined #git
15:33 PCatinean hey guys
15:33 PCatinean if I want to merge in a specific commit but not cherry-pick it, how can that be done?
15:35 absinthe joined #git
15:35 treia joined #git
15:35 m0viefreak PCatinean: it cannot
15:35 PCatinean hmm
15:36 m0viefreak cherry-pick is what you want
15:37 dreiss joined #git
15:39 UTAN_dev_ joined #git
15:40 PCatinean m0viefreak, even if I was to forward port some functionality?
15:41 PCatinean How do these guys do it for example? https://github.com/odoo/odoo/commit/de6aaeb5468f66283cd221f16e97affacd2a4146
15:41 thiago joined #git
15:42 PCatinean I mean where's the information indicating that the code comes from some other branch/repo and has been added to this codebase?
15:46 giraffe joined #git
15:47 hahuang61 joined #git
15:47 phanimahesh joined #git
15:51 dsdeiz joined #git
15:51 dsdeiz joined #git
15:53 trinakria joined #git
15:55 tjk joined #git
15:55 jast PCatinean: there's no such thing except for full merges
15:56 PCatinean jast, ok got it, so they just do a [merge] label and cherry-pick
15:56 jast you can, of course, mention what you did in the commit message, so you have an informal record at least
15:56 PCatinean jast, understood, thank you for the clarification
15:56 arand PCatinean: The commit you linked is a merge as indicated by the two parents.
15:58 jast yeah, I was speaking generally, not specifically about that merge commit you linked
15:59 jast when they merge in e0d33ce, they're also merging in all of its ancestors
15:59 PCatinean arand, sorry I didn't fully get that
15:59 PCatinean so it was not a cherry-pick
15:59 jast same is true for your own merges: you don't have to merge up until the tip of a branch, you can merge something older on the branch, but it will always pick up the stuff "before" that, too
16:01 arand Which is what it seems they're doing based on the "up to <sha1>" commit messages.
16:01 PCatinean Ah but that is from the sass, which is like a dev version of the current branch and can actually merge
16:01 PCatinean but from another branch that is vastly different, you cannot merge
16:02 PCatinean as you mentioend before
16:02 jast you can, but you'll probably get tons of conflicts and pain :)
16:02 jast in fact you can even merge history from two different repositories, but most of the time it doesn't really make sense
16:04 snowkidind joined #git
16:06 Derperperd joined #git
16:07 _0xbadc0de joined #git
16:09 pks joined #git
16:10 sdothum joined #git
16:15 chachasmooth joined #git
16:20 PCatinean jast, kinda makes sense yeah
16:21 PCatinean so just cherry-pick and provide the relevant message in the commit message
16:21 anuxivm joined #git
16:25 anuxivm left #git
16:25 SteffanW joined #git
16:28 raspado joined #git
16:31 [0xAA] joined #git
16:32 vuoto joined #git
16:33 afuentes joined #git
16:34 Darren_ joined #git
16:38 theoceaniscool joined #git
16:41 jozwior joined #git
16:44 pietv joined #git
16:48 octo8 joined #git
16:49 mischat joined #git
16:52 jnavila joined #git
16:53 timvisher joined #git
16:56 mda1 joined #git
16:56 sdothum joined #git
16:58 xkr47 joined #git
16:59 Ntemis joined #git
16:59 Ntemis hello
16:59 Lyqyd joined #git
16:59 Ntemis i want to merge 127 commits into one
16:59 Ntemis any help?
17:00 osse are they consecutive?
17:00 osse are they the 127 newest?
17:05 chipotle joined #git
17:06 lindenle joined #git
17:06 prg318 joined #git
17:07 prg3 joined #git
17:07 chachasmooth joined #git
17:07 Derperperd joined #git
17:08 cyan__ joined #git
17:19 madewokherd joined #git
17:19 nettoweb1 hello guys, after doing some git rebase master, I did git push -f origin master
17:19 nettoweb1 is there a way to revert it?
17:19 r00twrh joined #git
17:19 nidr0x joined #git
17:20 minikN joined #git
17:20 osse nettoweb1: no, but you can push up whatever was there before, maybe. Do  git show origin/master@{1}.  is that the right commit master should be at on the remove?
17:21 nettoweb1 Im sure I have some commit and they disappeared, I dont know if it was on rebase
17:21 nettoweb1 Some migrations disappeared
17:22 wCPO_ joined #git
17:23 hasc joined #git
17:23 gugah joined #git
17:23 osse find the commit origin/master should be at
17:25 jnavila joined #git
17:27 Jackneill joined #git
17:27 nettoweb1 it was not in master... I was working in a separted branch
17:27 nettoweb1 then:
17:27 nettoweb1 git rebase master
17:27 nettoweb1 then
17:28 osse i know
17:28 osse but you screwed up master
17:28 nettoweb1 git push -f
17:28 osse so it's master you need to fix
17:28 osse or are you asking about something else?
17:28 nettoweb1 git push -f screwed master?
17:28 nettoweb1 I thought it was pushing to marketplace
17:28 nettoweb1 marketplace = my branch
17:29 osse you force pushed master
17:30 thiago joined #git
17:31 nettoweb1 I dont think so, in github, my last commit on master was in december
17:32 osse maybe origin/master and master were equal to begin with. in that case nothing bad happened
17:32 osse how about actually reading what git push wrote ?
17:33 mentazoom joined #git
17:34 dikiaap left #git
17:35 nettoweb1 osse first, with git push I got this: ! [rejected]        marketplace -> marketplace (non-fast-forward)
17:36 nettoweb1 then I tried git push -f I got this:  + cf00e2e...93f1eb4 marketplace -> marketplace (forced update)
17:36 osse after running 'git push -f origin master' ?!!?
17:37 cdg joined #git
17:39 nettoweb1 no, I just run git push and then git push -f
17:39 canton7 beware that in older gits, and for some values of 'push.default', 'git push' (on its own) will try to push *all* branches where a matching branch exists on the remote
17:40 osse nettoweb1: ok that's not what you said...
17:40 nettoweb1 but these commands were in marktplace branch
17:40 bob joined #git
17:40 nettoweb1 sorry osse
17:40 justanotheruser joined #git
17:40 oskarkv joined #git
17:40 osse nettoweb1: ok, back to the beginning. do you want to undo the push -f? as if it never happened?
17:41 miczac_ joined #git
17:41 nettoweb1 yes, for one reason: Im not seeing some files that should be there, I think I miss them on git rebase. But first I'd like to revert that push -f
17:41 spacelord_ joined #git
17:42 osse nettoweb1: like i said about master, you cannot simply revert a push -f. the way to do it is another push -f that pushes what was there before
17:42 osse in this case:  git push -f origin cf00e2e:marketplace
17:42 nettoweb1 osse for example, I've renamed a table, and my schema show the new table name, but the migration that do this renaming was not there anymore
17:42 nettoweb1 ok, lemme try this
17:44 ploop joined #git
17:47 Guest54781 joined #git
17:47 hahuang61 joined #git
17:48 nettoweb joined #git
17:49 nettoweb thanks @osse now shows me that I m 31 commits to push and 5 to pull
17:49 nettoweb https://cl.ly/1W3D3e0R2X2B
17:49 NimeshNeema joined #git
17:50 mischat joined #git
17:51 cdown_ joined #git
17:51 nettoweb now, there is a way to revert my last git rebase master ? Because Im quite sure Im missing some file
17:51 nettoweb maybe on rebase I miss them
17:51 osse nettoweb: git reset --hard marketplace@{1}
17:51 osse unless you have made new commits to marketplace since the rebase
17:55 absinthe joined #git
17:57 nettoweb thanks osse
17:57 nettoweb I run git pull and now I can see my files, but with a lot of conflicts
17:58 nettoweb I'll fix them
17:58 nettoweb thanks
18:02 denimsoft joined #git
18:03 ramsub07 joined #git
18:04 dreiss joined #git
18:07 ianmethyst joined #git
18:10 Derperperd joined #git
18:10 Derperperd joined #git
18:12 mentazoom joined #git
18:15 ianmethyst joined #git
18:15 cdg_ joined #git
18:16 jnavila joined #git
18:16 rorro joined #git
18:17 denimsoft joined #git
18:20 denimsoft joined #git
18:22 justan0theruser joined #git
18:25 gautamsomani1 joined #git
18:25 dikiaap joined #git
18:25 miczac_ joined #git
18:29 kulelu88 joined #git
18:30 jmpp joined #git
18:30 denisMone joined #git
18:37 xkr47 joined #git
18:37 afuentes joined #git
18:37 UTAN_dev_ joined #git
18:37 malt3 joined #git
18:37 uebera|| joined #git
18:38 malt3 joined #git
18:39 inflames joined #git
18:39 Eryn_1983_FL joined #git
18:44 miczac_ joined #git
18:46 pietv joined #git
18:47 jost__ joined #git
18:47 WayToDoor joined #git
18:48 hahuang61 joined #git
18:53 justan0theruser joined #git
18:55 fahadash joined #git
19:11 Derperperd joined #git
19:14 thiago joined #git
19:15 absinthe joined #git
19:15 finalbeta joined #git
19:16 Ntemis osse: yes they are consecutive and newest
19:17 ph88_ joined #git
19:19 salamanderrake joined #git
19:23 ph88^ joined #git
19:23 nettoweb joined #git
19:23 Mikerhinos joined #git
19:24 PHPanos joined #git
19:32 Ozymandy joined #git
19:35 raspado joined #git
19:37 mischat joined #git
19:37 Pulp joined #git
19:42 jnavila joined #git
19:42 borkr joined #git
19:46 boubou joined #git
19:49 jeffreylevesque joined #git
19:53 gautamsomani joined #git
19:54 robattila256 joined #git
19:54 Lyqyd joined #git
20:07 Goplat joined #git
20:10 FederationOfNULL joined #git
20:12 Derperperd joined #git
20:14 shinnya joined #git
20:15 cdown joined #git
20:17 FederationOfNULL joined #git
20:19 KevinDF joined #git
20:23 Kevin_ joined #git
20:23 beneter joined #git
20:25 rudi_s joined #git
20:27 mischat joined #git
20:27 cdg joined #git
20:34 hahuang61 joined #git
20:37 ocbtec joined #git
20:37 jbitdrop joined #git
20:44 cdg joined #git
20:48 FederationOfNULL joined #git
20:48 aidalgol joined #git
20:54 cust joined #git
20:57 FederationOfNULL joined #git
21:01 LeBlaaanc joined #git
21:02 denisMone joined #git
21:03 re1_ joined #git
21:05 bmahe joined #git
21:07 marlun left #git
21:08 garethdaine joined #git
21:09 Derperperd joined #git
21:13 blackwind_123 joined #git
21:13 jarshvor joined #git
21:14 sdothum joined #git
21:14 ohcibi joined #git
21:16 dreiss joined #git
21:16 zerotresBR joined #git
21:21 jtri joined #git
21:22 jtri does the direction of a merge matter?  I merged someone elses branch into mine and didn't get their updates to a file, instead their changes were lost
21:23 hasc joined #git
21:23 grawity depends on the merge strategy
21:23 codemann- joined #git
21:23 zerotresBR joined #git
21:23 grawity the default (recursive) doesn't care; if it cannot resolve a conflict it asks *you* to do so
21:24 grawity unless of course if you used -X ours or even -s ours
21:25 jtri i didn't use any special strategy
21:26 jtri how can i see what strategy was used, or what is my default?
21:27 hasc_ joined #git
21:27 jtri hmm, what should i do in this case? it seems the merge is mucked up
21:28 jtri basically, i didn't use any merge strategy param, but the changes to a file were lost when i merged
21:28 jtri the very changes i was trying to get
21:29 jtri wait, the changes were in my branch, and when i merged with the other branch ot get other thigns the changes in my branch were lost
21:30 anuxivm joined #git
21:31 absinthe joined #git
21:31 jtri is this why people advise to use rebase when trying to get changes from the main branch?
21:31 jtri it really seems that git messed this up
21:32 jtri wondering what is the recovery strategy...
21:32 bremner !reflog
21:32 gitinfo The git reflog (`git log -g`) records the SHAs of your HEADs for 2+ weeks. `git checkout -b myrestore OLDSHA` and `git reset --hard OLDSHA` will relink to that state via a new and current branch respectively, see http://sethrobertson.github.com/GitFixUm/ for full details.  WARNING: reset --hard will trash any uncommitted changes!  Visualize with: gitk --all --date-order `git log -g --pretty=%H`
21:36 jtri does the default merge strategy favor theirs?
21:38 jtri since its the merge that failed, and that's the last thing, can i reset to the commit before the merge and then redo the merge?
21:38 bremner yes, assuming you haven't pushed
21:38 publio joined #git
21:40 jtri i have pushed
21:41 umpc joined #git
21:41 bremner well, the caveats of !rewrite  apply
21:41 gitinfo Rewriting public history is not recommended. Everyone who has pulled the old history will have to do work (and you'll have to tell them to), so it's infinitely better to just move on. If you must, you can use `git push --force-with-lease <remote> <branch>` to force (and the remote may reject that, anyway). See http://goo.gl/waqum
21:41 jtri so i pushed and one other developer pulled
21:41 bremner you may find it less hassle to cherry pick the changes from an old commit
21:42 rorro joined #git
21:43 timvisher joined #git
21:46 jtri can i use "get revert SHA-merge -m 1" to revert to the first parent of the merge?
21:46 jtri then remerge?
21:47 wcpan joined #git
21:47 [0xAA] joined #git
21:48 silnp joined #git
21:48 jtri ok, just trying to figure out what happend so i can avoid it and how to fix it now
21:49 Atm0spher1c joined #git
21:49 bremner I don't think revert will handle undoing the merge well.
21:50 jtri i did "git checkout develop" "git pull" "git checkout jared" "git merge develop" , and at that point the latest changes to StandaloneViewer were in develop, but were lost in my branch jared
21:50 miczac joined #git
21:51 jtri is that a bug in git?
21:51 jtri i can't see why the changes were lost for one
21:52 jtri b/c i'm working with another developer who eanted the code merge right away i pushed, and he pulled
21:53 bremner what did "git pull" merge into develop?
21:53 Wulf jtri: can you reproduce this?
21:56 jtri Wulf: not sure, trying
21:57 boombatower joined #git
21:58 Derperperd joined #git
21:59 onmeac joined #git
22:00 jtri bremner: origin/develop
22:00 jast if you revert, you can't re-merge. that's because 'merge' doesn't know the merge was reverted, the revert is just a plain commit that happens to undo the effects of the merge
22:01 variable joined #git
22:01 jtri jast: so what should we do?
22:01 jast what you're trying to do now: figure out what happened :)
22:02 jtri right
22:02 jtri there's that and fixing it...
22:03 jast let's see if we can get this figured out. in your 'jared' branch, does 'git log' show a commit "Merge develop [...]"?
22:05 jast actually, this is more interesting if you still have it: what output did you get from 'git merge develop'?
22:05 Derperperd joined #git
22:10 gambl0re joined #git
22:10 jtri http://dpaste.com/353GVPG
22:10 jtri that's the output of git log
22:11 jtri 97328c5 is the messed up merge
22:11 Lyqyd_ joined #git
22:12 jtri I don't still have the output of the merge
22:12 jast jtri: 56cccbf is a commit of yours?
22:12 jast made on your branch, I mean
22:12 jtri no, 56cccbf is the other person
22:13 jtri oh, wait, sorry, that is my branch
22:13 jast okay, because according to git it was made directly on your branch
22:13 jast ah, right
22:13 jtri the commit was made by the other person in my branch
22:13 jast good, then the *structure* of the merge is correct
22:14 jast you've got one file in particular where you notice the content isn't what it should be, right?
22:14 Lyqyd joined #git
22:14 jtri the file in question is StandaloneViewer.jsx
22:14 jast okay. I'd suggest you have a quick look at what was in it before the merge, on each side, to make sure there's nothing unexpected in either version:
22:14 jast git show 56cccbf:StandaloneViewer.jsx
22:14 jast git show c2b9f26:StandaloneViewer.jsx
22:15 jast (if it's not in the root of the repo, insert the path: abc123:path/to/file)
22:15 jtri did that, the file looks exactly as it does after the merge in c2b9f26
22:16 jast so, to make sure I'm understanding the situation correctly: which changes got lost in the merge? the ones from develop, or the ones from your branch?
22:16 jantje joined #git
22:16 jtri yep, did that
22:16 jtri the changes from 56cccbf got lost
22:17 jameser joined #git
22:17 jtri is it bc/ the time stamp on the merge is later than the time stamp on the file?
22:18 jast in 'git diff jared^ jared StandaloneViewer.jsx', does the diff contain exactly the missing changes?
22:18 jast nah, git doesn't care about timestamps
22:20 jtri that diff doesn't work for me
22:20 jast what does it do?
22:20 jtri wiat, i need the full path
22:20 Kevin__ joined #git
22:20 LeBlaaanc joined #git
22:20 jast relative to current dir in your shell
22:21 jtri git diff jared^ jared src/javascript/main/module-viewer/StandaloneViewer.jsx show nothing empty
22:22 Sri[m] joined #git
22:22 jtri so that diff makes no sense!?
22:22 wget Hi guys. I was wondering if there was a command to  git clone --recursive and git submodule update --remote at the same time?
22:23 jast that would indicate that the merge didn't actually change the file, compared to your previous commit in 'jared'
22:23 jast it would also indicate that the merge didn't bring in anything from 'develop'
22:23 jast at least in that file
22:24 wget I want to prevent my parent git repository to be linked against a particular revision of the submodule repository.
22:24 LeBlaaanc joined #git
22:25 osse Ntemis: git reset --soft HEAD~127 && git conmit
22:25 aax joined #git
22:26 Ntemis this will merge the commits without me need to rename one by one to squash
22:26 Ntemis ?
22:26 jtri here's the two results of the git show SHA:file you asked for above: http://dpaste.com/165F9NP http://dpaste.com/3FW8FCB
22:26 jtri which indicates something differnt than the diff
22:26 jast wget: as far as I know, the only way to do that is to update .gitmodules in the parent repo to include the 'submodule.foo.branch' setting
22:27 spacelord_ joined #git
22:27 wget jast: yep, the progit book mentions  git config -f .gitmodules submodule.<name of the submodule>.branch <name of the branch>
22:28 Ntemis osse: ?
22:28 BlaXpirit Ntemis, yes
22:28 jast jtri: I can't tell from what I've seen so far, I'd need the output of this, too: git show 97328c5:thatfile (<- me being lazy). that would be the final version according to the merge.
22:28 morsecat joined #git
22:28 Ntemis lovely
22:28 davimore joined #git
22:28 Ntemis thank you
22:28 BlaXpirit Ntemis, it undoes the commits but keeps the current state of files
22:29 anuxivm left #git
22:29 Ntemis ty
22:29 BlaXpirit (then you just commit it)
22:30 Kevin_ joined #git
22:30 LeBlaaanc joined #git
22:31 osse Ntemis: I just answered your squash question
22:31 Ntemis yes u did
22:31 Ntemis thank you
22:33 jameser joined #git
22:34 jast jtri: and to complete the picture, the output from this would tell us what base version merge used: git show $(git merge-base 56cccbf c2b9f26):thatfile -- that should be enough to figure out what merge thought when it did what it did :)
22:35 hahuang61 joined #git
22:36 jtri http://dpaste.com/2KMN621
22:36 jast okay, give me a second with this :)
22:36 jtri jast: I have to go in like 2 minutes :(
22:37 miczac_ joined #git
22:38 mischat joined #git
22:38 Kevin__ joined #git
22:40 jast jtri: I don't think we'll figure it out in two minutes, we'll probably need a little more back and forth. some other time, maybe...
22:40 jast perfect timing :)
22:42 FelixVi joined #git
22:45 felix__ joined #git
22:46 FelixVi joined #git
22:47 FelixVi joined #git
22:52 Tobbi joined #git
23:00 Kevin_ joined #git
23:01 fmeerkoetter joined #git
23:06 Vaelatern joined #git
23:08 Debyte joined #git
23:11 chachasmooth joined #git
23:14 albel727 joined #git
23:14 Cthalupa joined #git
23:14 cdg_ joined #git
23:15 Orion3k joined #git
23:16 Darren_ joined #git
23:20 Doginal joined #git
23:25 est31 joined #git
23:26 est31 hi there, I've got a weird issue with git. I'm no beginner but somehow its tools don't help me
23:26 est31 specifically I saw this commit on github https://github.com/rust-lang/rust/commit/164f0105bb65f31b89e5fb7f368c9e6f5833a3f8
23:26 est31 the commit adds a line to src/libcollections/lib.rs
23:27 est31 I checked out master in a local clone, and couldn't find that line
23:27 est31 so I wondered how it got removed
23:27 est31 so I did git log --full-diff -p src/libcollections/string.rs
23:27 est31 and then asked less to search for safe_suggestions
23:27 est31 less didn't find it.
23:28 est31 next try, I've done git log src/libcollections/string.rs
23:28 est31 the commit doesn't show up!
23:28 est31 note that when I do git log without any arguments, I can find the commit
23:28 est31 what did I do wrongly?
23:31 chachasmooth joined #git
23:31 jast est31: you say you searched for "safe_suggestions" but the line actually adds "safe_suggestion"
23:32 jmpp joined #git
23:32 jmpp joined #git
23:32 est31 searching git log for safe_suggestion doesnt help either
23:32 BlessJah est31: does "git branch -a --contains <hash>" return anything?
23:32 est31 git log src/libcollections/string.rs | grep safe_suggestion
23:32 est31 output is empty
23:33 jast anyway, without looking at the repo, one possibility is that the file changed its name later, try adding the --follow flag (for a single file arg)
23:33 est31 BlessJah: it contains  a bunch of lines, also one with " * master"
23:33 albel727 joined #git
23:33 jast hmm, actually --follow goes the other way
23:34 est31 I'm not aware of such a change, the file is still present
23:34 est31 and when I do git log on the file, it shows me commits from 2014
23:34 BlessJah git log -S'line that was removed'?
23:34 est31 so well before that commit.
23:34 jast okay, I'm going to grab a copy of that repo
23:35 est31 BlessJah: that helped
23:35 est31 apparently commit c11fe553df269d6f47b4c48f5c47c08efdd373dc removed it again
23:35 BlessJah there is also -G, that will reveal renames
23:35 est31 https://github.com/rust-lang/rust/commit/c11fe553df269d6f47b4c48f5c47c08efdd373dc
23:36 est31 but why didn't git log src/libcollections/lib.rs show it?
23:36 est31 does it have to do with merge commits?
23:37 BlessJah branch --contains, because I suspected the commit was rebased/dropped, -S and -G are build-in diff|grep for git log
23:37 diogenese joined #git
23:37 BlessJah jast: grabbed a copy? was there a rename? or sth?
23:38 jast well, 'git log <file>' does omit merges if the file is identical before and after the merge, I believe, see if --full-history gives a different result
23:38 est31 okay, that explains it
23:38 est31 thanks jast, BlessJah!
23:39 BlessJah no problem
23:39 est31 --full-history indeed shows it
23:39 jast BlessJah: I just meant I cloned the repo to have a look at it :)
23:39 est31 left #git
23:41 BlessJah yep, I wanted to know if ya found anythin' sneaky in there
23:42 chachasmooth joined #git
23:44 Debyte joined #git
23:46 jast didn't look that hard after all
23:46 jast *I didn't
23:48 BlessJah me neither, checking this on 53x23 phone terminal would be challenging for sure
23:53 jason237 joined #git
23:53 GT4066 joined #git
23:53 boutcher joined #git
23:57 mostlybadfly joined #git
23:58 BlackMaria joined #git
23:59 boombatower joined #git

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