[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Savannah-hackers-public] savane git cannot be committed
|
From: |
Karl Berry |
|
Subject: |
Re: [Savannah-hackers-public] savane git cannot be committed |
|
Date: |
Sat, 5 Oct 2013 20:51:37 GMT |
I wonder whether it is actually useful to push from address@hidden
Yes, at least to me it is. Whenever I push from other places I end up
in some kind of git hell.
Beyond that, it is the only safe thing I've found to do. Like I asked
before, how you can tell what git pull will bring in?
k
- Re: [Savannah-hackers-public] savane git cannot be committed, (continued)
Re: [Savannah-hackers-public] savane git cannot be committed, Tomasz Konojacki, 2013/10/03
Re: [Savannah-hackers-public] savane git cannot be committed, Karl Berry, 2013/10/04
- Re: [Savannah-hackers-public] savane git cannot be committed, Tomasz Konojacki, 2013/10/05
- Re: [Savannah-hackers-public] savane git cannot be committed, Ineiev, 2013/10/05
- Re: [Savannah-hackers-public] savane git cannot be committed,
Karl Berry <=
- Re: [Savannah-hackers-public] savane git cannot be committed, Ineiev, 2013/10/06
- Re: [Savannah-hackers-public] savane git cannot be committed, Karl Berry, 2013/10/07
- Re: [Savannah-hackers-public] savane git cannot be committed, Ineiev, 2013/10/08
- Re: [Savannah-hackers-public] savane git cannot be committed, Karl Berry, 2013/10/08
- Re: [Savannah-hackers-public] savane git cannot be committed, Bob Proulx, 2013/10/10
Re: [Savannah-hackers-public] savane git cannot be committed, Bob Proulx, 2013/10/05