Re: [git-users] Git commit

[Boubakary Wadjiri Mohammadou]

I did not use the git commit -m properly. The message i wrote after -m was
not valid

On Thu, Feb 2, 2017 at 12:41 AM, Gergely Polonkai 
wrote:

> That’s great! Would you tell us, and especially people who visit the
> archives later, what the problem was?
>
> On Wed, Feb 1, 2017, 23:29 Boubakary Wadjiri Mohammadou 
> wrote:
>
>> Thanks i have arranged the problem.
>>
>> On Wed, Feb 1, 2017 at 10:28 PM, Philip Oakley 
>> wrote:
>>
>> Boubakary,
>> Is your 'commit' command an alias?
>>
>> Philip
>>
>> - Original Message -
>> *From:* Gergely Polonkai 
>> *To:* Git for human beings 
>> *Sent:* Wednesday, February 01, 2017 8:46 PM
>> *Subject:* Re: [git-users] Git commit
>>
>> My guess is, you provide a commit message that contains an exclamation
>> mark, and you don’t quote it. The error message is giwen by bash, not git.
>> So instead of
>>
>> git commit -m Message!
>>
>> try
>>
>> git commit -m "Message!"
>>
>> (You will need the quotes anyway if your commit message contains multiple
>> words.)
>>
>> If I’m wrong, could you show us what exact command did you use? Without
>> that, it’s hard to answer your question.
>>
>> Best,
>> Gergely
>>
>> On Wed, Feb 1, 2017, 16:23 Boubakary Wadjiri Mohammadou <
>> bwmr...@gmail.com> wrote:
>>
>> Hello guys i have difficulties in using the git commit command. Whenever
>> i commit i receive this message "bash: !: event not found"
>>
>> I am using a Windows 10 OS. Need Help. Thanks
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Git for human beings" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to git-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Git for human beings" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to git-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Git for human beings" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/
>> topic/git-users/9MeRUaAN9Mo/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> git-users+unsubscr...@googlegroups.com.
>>
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Git for human beings" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to git-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Git for human beings" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/git-users/9MeRUaAN9Mo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Synchronizing air gapped git repositories using bundles

[Philip Oakley]

Hi Lowell,

You can use all of the options in the rev-list for selecting which commits are 
in the bundle (which is just a thin wrapper around the pack file that would be 
sent over the wire). 

You can include more commits in the bundle than you need [1], that is, have an 
overlap. One option is simply to use the --since= option as a way of 
ensuring you go far enough back in history. Plus the --all to get everything 
after tha date [2].

I suspect that part of the problem is finding a way of recording what has been 
transferred in the three way transfer - I'd suggest it's just as easy to use a 
small note book (or formal admin log) for recording the date of transfers and 
use that to guide the bundle creation.

Plus you can always stack up the bundles, so can fetch first from the oldest 
bundle, and then from the newer bundle, etc. 

I see you have the typical 'transfer review' process for the bundle exchange 
(implies a certain kind of environment ;-) - does it ever fail/reject the 
transfer? or is it simply making sure it is what you thought it was and have 
recorded the transfer correctly (I expect it's actually the latter). If you get 
true rejection you have more issues.

I don't really think you need a special 'script' (beyond satisfying some 
edict), as the bundle and fetch commands should be sufficient for doing the 
transfer.

Probably the biggest issue at that point is having a standardised naming 
convention for the bundle file, e.g. server--.bndl so 
that you know where it came from, where the --since cut point was, and when it 
was created.

Then it becomes fairly easy to import/fetch from the bundle acording to the 
carefully mandated process. 

Philip

[1] https://git-scm.com/docs/git-bundle
It is okay to err on the side of caution, causing the bundle file to contain 
objects already in the destination, as these are ignored when unpacking at the 
destination.
[2] 
http://stackoverflow.com/questions/11792671/how-to-git-bundle-a-complete-repo
  - Original Message - 
  From: Lowell Alleman 
  To: Git for human beings 
  Sent: Wednesday, February 01, 2017 9:58 PM
  Subject: [git-users] Synchronizing air gapped git repositories using bundles


  I have 3 separate air-gapped git repositories (hosted on local GitHub 
enterprise) that I'm trying to keep in sync.   Currently, I'm using "git 
bundle" to push revisions back and forth, which worked fairly well with just 2 
repositories, but I'm struggling a bit since the 3rd (and final) repository has 
been added to the mix.  I was using a single tag to track the point of last 
export as noted in the "git bundle" docs, but I'm struggling to make that scale 
with 2+ total repositories. 


  In terms of information flow, we've deemed one of the repositories as 
"primary" and the other two as "secondary" repositories.  So in a sense we are 
using the "primary" repository like a development and merging area so that all 
changes go through the primary repository and trickle down to the secondary 
repositories.  Changes are always pushed upstream to primary, and then synced 
down to the other secondary repository. 


  Please note that our use of git is more like a "versioned file system" than 
the typical developer use case.  I go on to explain that a bit more later, but 
wanted to get to my main question before everyone gives up on reading this 
really long and complicated explanation of the mess I made. 


  Q:  Does anyone know of any existing scripts, documented methods, or best 
practices to follow when syncing a branch between multiple air-gapped 
repositories?


  How we are using git:  As noted above, this is NOT a typical 
development-centered use-case.  Branching is very infrequent, and most work is 
done on the "master" branch in each repository.  Unlike typical 
developer-centric approaches, each clone (working copy) ends up tied to a 
specific server, rather than a single developer.  So multiple users end up 
working in the same working copy and committing code from one place.  The team 
is small and the changes are infrequent enough that this works for us, despite 
the atypical and less-than-ideal use case.



  How we are using branches:   We treat each repository as if it has just one 
branch, a single "master".  However, because of the synchronization 
requirements, we create special purpose branches in each repository that 
essentially mirror the master branches of the other repositories.  So the 
primary repository has 2 mirrored branches, one for each of the secondary 
repositories.  And each secondary repository has a single mirrored branch that 
represents the primary (upstream) repository.  (By convention, we have agreed 
never to synchronize revisions directly between the two secondary 
repositories.)  Local changes are never applied to a mirrored repository 
branch, so that it should match the "master" branch of the mirrored repository 
exactly.  (That is, the only changes to these mirrored branches are 
fast-forward only 

Re: [git-users] Git commit

[Gergely Polonkai]

That’s great! Would you tell us, and especially people who visit the
archives later, what the problem was?

On Wed, Feb 1, 2017, 23:29 Boubakary Wadjiri Mohammadou 
wrote:

> Thanks i have arranged the problem.
>
> On Wed, Feb 1, 2017 at 10:28 PM, Philip Oakley 
> wrote:
>
> Boubakary,
> Is your 'commit' command an alias?
>
> Philip
>
> - Original Message -
> *From:* Gergely Polonkai 
> *To:* Git for human beings 
> *Sent:* Wednesday, February 01, 2017 8:46 PM
> *Subject:* Re: [git-users] Git commit
>
> My guess is, you provide a commit message that contains an exclamation
> mark, and you don’t quote it. The error message is giwen by bash, not git.
> So instead of
>
> git commit -m Message!
>
> try
>
> git commit -m "Message!"
>
> (You will need the quotes anyway if your commit message contains multiple
> words.)
>
> If I’m wrong, could you show us what exact command did you use? Without
> that, it’s hard to answer your question.
>
> Best,
> Gergely
>
> On Wed, Feb 1, 2017, 16:23 Boubakary Wadjiri Mohammadou 
> wrote:
>
> Hello guys i have difficulties in using the git commit command. Whenever i
> commit i receive this message "bash: !: event not found"
>
> I am using a Windows 10 OS. Need Help. Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Git for human beings" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/git-users/9MeRUaAN9Mo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> git-users+unsubscr...@googlegroups.com.
>
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Git commit

[Boubakary Wadjiri Mohammadou]

Thanks i have arranged the problem.

On Wed, Feb 1, 2017 at 10:28 PM, Philip Oakley  wrote:

> Boubakary,
> Is your 'commit' command an alias?
>
> Philip
>
> - Original Message -
> *From:* Gergely Polonkai 
> *To:* Git for human beings 
> *Sent:* Wednesday, February 01, 2017 8:46 PM
> *Subject:* Re: [git-users] Git commit
>
> My guess is, you provide a commit message that contains an exclamation
> mark, and you don’t quote it. The error message is giwen by bash, not git.
> So instead of
>
> git commit -m Message!
>
> try
>
> git commit -m "Message!"
>
> (You will need the quotes anyway if your commit message contains multiple
> words.)
>
> If I’m wrong, could you show us what exact command did you use? Without
> that, it’s hard to answer your question.
>
> Best,
> Gergely
>
> On Wed, Feb 1, 2017, 16:23 Boubakary Wadjiri Mohammadou 
> wrote:
>
>> Hello guys i have difficulties in using the git commit command. Whenever
>> i commit i receive this message "bash: !: event not found"
>>
>> I am using a Windows 10 OS. Need Help. Thanks
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Git for human beings" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to git-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Git for human beings" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Git for human beings" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/git-users/9MeRUaAN9Mo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> git-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] How to improve the Git status performance

[Philip Oakley]

- Original Message - 
  From: Stephen Morton 
  To: Git for human beings 
  Cc: philipoak...@iee.org 
  Sent: Wednesday, February 01, 2017 8:28 PM
  Subject: Re: [git-users] How to improve the Git status performance


  On Wednesday, 1 February 2017 00:42:51 UTC-5, Ravalika wrote:
Thank you Philip and Mark.


We are using Linux servers. We can't have local disk, as it is corporate 
setup. 
We have our project shares on build servers across LAN only


I have tried sparse checkout and other options but not much improvement on 
git status. 
git status -uno
git update-index --untracked-cache and git update-index --split-index




  Sounds to me like the issue is "git status performance when repo is on a 
network drive".
  What you will need to do is this
- Find out what sort of network mounting you have
- Find out what sort of caching you have, and what is available to you.
- You started to do some profiling on 'git status' performance that seems 
to indicate that caching plays a big part. You could confirm this by observing 
how subsequent 'git status' commands are faster, but that when you drop the 
cache, performance goes back down to the original slow time.
- Talk to your IT people to find out if anything can be sped up.
- Do some research on git's performance in this situation


  My gut feeling is that you are basically out of luck. Git does a lot of 
filesystem calls and I suspect that performance on a repo with lots and lots of 
files is going to be extra-slow when network mounted. (By contrast, my huge 
corporate repo on a locally-mounted SSD on linux can do a 'git status' in 
<0.1s.)



  Steve
Also, talk with your IT to determine if you can get some local machine space to 
host your local copy (then just use push to the server repo for one shot 
updates and 'backup'). Explain that it's the way Git was designed - to allow 
local working when off network. Failing that, use it as a lever to improve the 
network performance.

Philip

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] Git commit

[Philip Oakley]

Boubakary,
Is your 'commit' command an alias? 

Philip
  - Original Message - 
  From: Gergely Polonkai 
  To: Git for human beings 
  Sent: Wednesday, February 01, 2017 8:46 PM
  Subject: Re: [git-users] Git commit


  My guess is, you provide a commit message that contains an exclamation mark, 
and you don’t quote it. The error message is giwen by bash, not git. So instead 
of

  git commit -m Message!

  try

  git commit -m "Message!"

  (You will need the quotes anyway if your commit message contains multiple 
words.)

  If I’m wrong, could you show us what exact command did you use? Without that, 
it’s hard to answer your question.

  Best,
  Gergely



  On Wed, Feb 1, 2017, 16:23 Boubakary Wadjiri Mohammadou  
wrote:

Hello guys i have difficulties in using the git commit command. Whenever i 
commit i receive this message "bash: !: event not found"


I am using a Windows 10 OS. Need Help. Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Git for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


  -- 
  You received this message because you are subscribed to the Google Groups 
"Git for human beings" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to git-users+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] where is the .git file?

[Ben David]

I only crapped on their heads because they are already crapping on 
everyone's head that stops by here.  If you don't want crap in this forum, 
don't produce it and you won't see any.  What you are seeing in my response 
is a reflection of the crap you are producing here.

The cogent answer is provided in the link I gave - an actual answer to the 
question that anyone coming here can follow and see.  I could be more 
constructive if I wanted to, but again my lack of constructiveness is a 
reflection to you of just how unconstructive the information on this thread 
was - if you produced constructive information you wouldn't get what 
appears to you to be unconstructive feedback.  Sometimes tough love takes a 
tough form, and people need to hear they suck so they have room to consider 
they can improve.  I can be appreciative and insulting at the same time, if 
you cannot that's your deal, but projecting it onto me doesn't make it true.

Sorry, but just because people do something for free or on a volunteer 
basis doesn't mean they can take a dump on a public street and not have it 
pointed out to them.

I would suggest you guys cut the BS, and then you won't get any BS in 
return.  Instead of "trying" to help people, maybe actually do it?

As for me, I'm outta here.

Blacklisted.  Reason: sux.

On Tuesday, January 31, 2017 at 11:14:37 PM UTC-8, Konstantin Khomoutov 
wrote:
>
> On Tue, 31 Jan 2017 15:18:44 -0800 (PST) 
> Ben David  wrote: 
>
> > I will absolutely run away with this - all of your answers suck, 
> [...] 
> > I understand you all are attempting to help, 
>
> No, you don't -- see below. 
>
> > and appreciate the attempt even if I'm a bit belligerent here. 
>
> No, you're being actively insulting, full stop. 
>
> > On the other hand, the answers sucked, wasted my time, and confused me 
> > more than helped. 
>
> That's the thing you don't understand about how this stuff works. 
> This mailing list is a volunteer effort.  We may suck at helping anyone 
> asked for help but you didn't pay anyone to spend *their* time on trying 
> to help.  It's like being starved, knocking on someone's door asking 
> for food, eating it and then complaining it wasn't quite to your taste 
> or not heated up enough. 
>
> Seeking for help on public forums is a "take it or leave it" thing. 
>
> > And on the internets here, it could be wasting the time of thousands 
> > of people.  All of that cumulative human time that could have been 
> > put into something constructive burned on unclear b.s. written by 
> > individuals well-intended, but who could remain silent if they can't 
> > communicate or listen well enough to produce a cogent answer. 
>
> ...so here came shining you and produced a cogent answer? 
>
> Uh, wait, where it is?  No, instead you spent time and effort to produce 
> two mail messages intended to crap onto the heads of everyone attempted 
> to help the OP. 
>
> Come on, please cut this BS on this list.  If you can't be constructive 
> (you can't) but feel an irresistible urge to teach volunteers how to do 
> things, please go and write a blog post or two. 
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] Git commit

[Boubakary Wadjiri Mohammadou]

Hello guys i have difficulties in using the git commit command. Whenever i 
commit i receive this message "bash: !: event not found"

I am using a Windows 10 OS. Need Help. Thanks

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.