Hi Michal,
Michal Maruska wrote:
> sid has version 1:2.47.2-0.1
> https://packages.debian.org/source/sid/git mentions as git source:
> https://repo.or.cz/w/git/debian.git/
>
> which indeed has the relevant branch:
> https://repo.or.cz/git/debian.git/shortlog/refs/heads/debian-sid
>
> but it's
On 10/7/23 01:51, to...@tuxteam.de wrote:
On Fri, Oct 06, 2023 at 01:44:34PM -0700, Mike Castle wrote:
Something I played with recently was
https://packages.debian.org/stable/vcs/git-filter-repo
Yes, it does work. My typical use case is when someone has put a
password in the repo you don't eve
On Fri, Oct 06, 2023 at 01:44:34PM -0700, Mike Castle wrote:
> Something I played with recently was
> https://packages.debian.org/stable/vcs/git-filter-repo
Yes, it does work. My typical use case is when someone has put a
password in the repo you don't even want to have in the history.
But you ar
Something I played with recently was
https://packages.debian.org/stable/vcs/git-filter-repo
But you definitely want to run tests on real data before you decide
that deleting old data saves your anything, particularly with respect
to time.
If git is so efficient at storing this kind of data, then
>> `git gc` does delete the old data (if it's not reachable any more).
> And it is very expensive. My point exactly.
It's fairly expensive indeed, but it's usually an operation that is not
very time-sensitive: it can usually be delayed to a convenient time, and
you can run it infrequently and as
Stefan Monnier (12023-10-06):
> `git gc` does delete the old data (if it's not reachable any more).
And it is very expensive. My point exactly.
> BTW, if you want to (ab)use a Git repository to do backups, you should
> definitely look at `bup`.
Thanks, it might be exactly what I am looking for.
> Have you tried? The very principle of Git makes it necessary, to remove
> or update old data, to rewrite the whole subsequent history.
> Furthermore, it is done by creating a new branch, the original data is
> not actually deleted.
`git gc` does delete the old data (if it's not reachable any mor
john doe (12023-10-06):
> Please elaborate on why Git is so bad at removing data from a single
> repository?
Have you tried? The very principle of Git makes it necessary, to remove
or update old data, to rewrite the whole subsequent history.
Furthermore, it is done by creating a new branch, the or
On 10/6/23 13:26, Nicolas George wrote:
john doe (12023-10-06):
I do not understand why you would want multiple repos, to me this looks
like this would fit the bill for a Git branching workflow.
Please elaborate. How do you work around the fact that Git is terrible
at removing data with a sing
Max Nikulin (12023-10-06):
> I have no idea if it is possible to do it in place, but "git clone" and "git
> fetch" have the --depth option. So you can specify how many last commits you
> would like to have in the cloned repository. Using "git rebase
I know. They only allow to keep the last commits
john doe (12023-10-06):
> I do not understand why you would want multiple repos, to me this looks
> like this would fit the bill for a Git branching workflow.
Please elaborate. How do you work around the fact that Git is terrible
at removing data with a single repository?
Regards,
--
Nicolas
On 10/6/23 11:14, Nicolas George wrote:
Hi.
There is a project I have that requires some scripting, but I am
wondering if somebody already did something similar and there is a
package that I can just apt-get install.
The idea is to use Git to store backups of text files that change rather
rarel
On 06/10/2023 16:14, Nicolas George wrote:
Unfortunately, Git is very bad at removing old data
I have no idea if it is possible to do it in place, but "git clone" and
"git fetch" have the --depth option. So you can specify how many last
commits you would like to have in the cloned repository.
On Fri, 2023-08-25 at 22:36 +, Russell L. Harris wrote:
> If pushing from PRODUCTION is more reliable or less trouble-prone than
> pulling from BACKUP, kindly explain to me, and I shall change.
Another consideration is that to pull from PRODUCTION requires it to be
running a service (e.g. ssh)
On Sat, Aug 26, 2023 at 08:10:20AM -0300, Eduardo M KALINOWSKI wrote:
[...]
> The reliability should be the same, but you cannot push to a non-bare
> repository. At least not in the standard configuration, but git being git
> I'm sure there's a way to override that.
Actually, if the push doesn't
On 25/08/2023 19:36, Russell L. Harris wrote:
But for me, the only purpose of the backup repository is to ensure
against data loss due to a catastrophic event such as drive failure on
my production host.
If pushing from PRODUCTION is more reliable or less trouble-prone than
pulling from BACKUP,
On Fri, Aug 25, 2023 at 09:40:19PM +0100, Tixy wrote:
> On Fri, 2023-08-25 at 19:47 +0200, john doe wrote:
> > On 8/25/23 13:44, Tixy wrote:
> > > On Fri, 2023-08-25 at 10:47 +0200, to...@tuxteam.de wrote:
> > > > Yes, I think a bare remote is the way to go in this context
> > >
> > > You can make
On Fri, Aug 25, 2023 at 10:36:33PM +, Russell L. Harris wrote:
> As best I understand it (and kindly correct me if I am mistaken), a
> bare repository is a central repository used by a group of developers.
> Each developer has his own repository, and no developer ``owns'' the
> central reposito
On Fri, Aug 25, 2023 at 09:54:02AM +0200, Loris Bennett wrote:
Does a bare remote to which you simply push not already provide you with
an adequate backup? One you have made a number of commits, you can just
push them to the remote.
I am old and my fingers sometimes strike the wrong keys. (In
On Fri, 2023-08-25 at 19:47 +0200, john doe wrote:
> On 8/25/23 13:44, Tixy wrote:
> > On Fri, 2023-08-25 at 10:47 +0200, to...@tuxteam.de wrote:
> > > Yes, I think a bare remote is the way to go in this context
> >
> > You can make a repo bare by editing it's config file (.git/config) to
> > have
On 8/25/23 13:44, Tixy wrote:
On Fri, 2023-08-25 at 10:47 +0200, to...@tuxteam.de wrote:
Yes, I think a bare remote is the way to go in this context
You can make a repo bare by editing it's config file (.git/config) to
have 'bare = true' instead of 'bare = false' under the '[core]'
>
General
On Fri, 2023-08-25 at 10:47 +0200, to...@tuxteam.de wrote:
> Yes, I think a bare remote is the way to go in this context
You can make a repo bare by editing it's config file (.git/config) to
have 'bare = true' instead of 'bare = false' under the '[core]'
section. I do this after copying the .git d
On 8/25/23 09:04, Russell L. Harris wrote:
On Fri, Aug 25, 2023 at 07:24:59AM +0100, Tixy wrote:
On Thu, 2023-08-24 at 22:24 +, Russell L. Harris wrote:
I'm also a bit confused about doing it this way. The usual workflow
with git is to 'push' to the remote repository, which is in fact what
y
On Fri, Aug 25, 2023 at 09:54:02AM +0200, Loris Bennett wrote:
[...]
> Does a bare remote to which you simply push not already provide you with
> an adequate backup? One you have made a number of commits, you can just
> push them to the remote.
Yes, I think a bare remote is the way to go in t
"Russell L. Harris" writes:
> On Fri, Aug 25, 2023 at 07:24:59AM +0100, Tixy wrote:
>>On Thu, 2023-08-24 at 22:24 +, Russell L. Harris wrote:
>>> #!/bin/bash
>>> # post-commit
>>> # 2023.08.24 2200gmt
>>>
>>> ssh backup "git pull"
>>> exit 0
>
>>You could omit the 'exit 0' so it returns the e
On Fri, Aug 25, 2023 at 07:24:59AM +0100, Tixy wrote:
On Thu, 2023-08-24 at 22:24 +, Russell L. Harris wrote:
#!/bin/bash
# post-commit
# 2023.08.24 2200gmt
ssh backup "git pull"
exit 0
You could omit the 'exit 0' so it returns the error code from the ssh
command, that way you'll get som
On Thu, 2023-08-24 at 22:24 +, Russell L. Harris wrote:
> #!/bin/bash
> # post-commit
> # 2023.08.24 2200gmt
>
> ssh backup "git pull"
> exit 0
>
You could omit the 'exit 0' so it returns the error code from the ssh
command, that way you'll get some feedback from failures to backup
which you
On Tue, Aug 22, 2023 at 12:59:18AM -0400, Karl Vogel wrote:
me% cat try
#!/bin/sh
export PATH=/usr/local/bin:/bin:/usr/bin
ssh -q -c aes128-...@openssh.com -i $HOME/.ssh/bkup_ed25519 \
bkup "logger -t autopull git pull whatever"
exit 0
I am grateful for the recommendations
On Tue, 22 Aug 2023 16:31:58 +0200
wrote:
> On Tue, Aug 22, 2023 at 09:16:47AM -0500, John Hasler wrote:
> > Christoph writes:
> > > I have almost the same setup and use local git repositories. Instead
> > > of syncing them by the git tools I use rsync to update the backup from
> > > time to tim
On Tue, 22 Aug 2023 09:28:00 +0200
john doe wrote:
> To me you only update upstream by pushes and never by pulling!
>
> So my suggestion in your case would be:
> - One repo to work in and to push to upstream
> - One upstream bare repo
This is essentially what I do. My master repo, which the OP
On Tue, Aug 22, 2023 at 03:00:33AM +, Russell L. Harris wrote:
> My needs are simple. I need two git repositories.
>
> The first is my work space, into which periodically I commit the
> article on which I am working.
>
> The second repository is my backup; it resides on another machine.
> Seve
On 2023-08-22 03:00 +, Russell L. Harris wrote:
> After much searching and reading, I have not discovered how to set up
> a pair of git repositories to work together.
>
> I write articles for publication. I typically spend anywhere from
> several hours to many days on each article. It is fru
On Tue, Aug 22, 2023 at 09:16:47AM -0500, John Hasler wrote:
> Christoph writes:
> > I have almost the same setup and use local git repositories. Instead
> > of syncing them by the git tools I use rsync to update the backup from
> > time to time. This is a dumb method but it works.
>
> This is wh
Christoph writes:
> I have almost the same setup and use local git repositories. Instead
> of syncing them by the git tools I use rsync to update the backup from
> time to time. This is a dumb method but it works.
This is what I do as well.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On 8/22/23 05:00, Russell L. Harris wrote:
After much searching and reading, I have not discovered how to set up
a pair of git repositories to work together.
This makes no sense, that is what Git is for! :)
In the past, I have found git to be a very good solution. But now I
am moving to a n
Am Tue, Aug 22, 2023 at 03:00:33AM + schrieb Russell L. Harris:
Hello Russel,
I cannot answer your question directly but show what I am doing now.
> After much searching and reading, I have not discovered how to set up
> a pair of git repositories to work together.
>
> I write articles for pu
On Mon, Aug 21, 2023 at 11:01:21PM -0400, Russell L. Harris wrote:
> I write articles for publication. I typically spend anywhere from
> several hours to many days on each article. It is frustrating to work
> for an hour or two on a paragraph or a page and then accidentally to
> erase what I have
On Thu, May 11, 2023 at 07:05:21PM -0400, Stefan Monnier wrote:
> > git remote remove origin
> > # this re-adds it
> > git remote add origin
>
> Better go with
>
> git remote set-url origin
Right :)
Cheers
--
t
signature.asc
Description: PGP signature
> git remote remove origin
> # this re-adds it
> git remote add origin
Better go with
git remote set-url origin
-- Stefan
On 5/10/23 05:47, William Torrez Corea wrote:
Command:
git push master origin
I want upload my change to branch MAIN but when i want upload my change i
get the following error:
remote: Support for password authentication was removed on August 13, 2021.
remote: Please see
https://docs.githu
On 2023-05-10 05:49:19 +0100, Tim Woodall wrote:
> On Tue, 9 May 2023, William Torrez Corea wrote:
>
> > Command:
> >
> > git push master origin
> > >
>
> shouldn't that be git push origin master? Or even origin main?
Or in general, simply "git push", since the current branch and the
associate
On Tue, May 09, 2023 at 09:47:45PM -0600, William Torrez Corea wrote:
> Command:
>
> git push master origin
> >
>
> I want upload my change to branch MAIN but when i want upload my change i
> get the following error:
>
> remote: Support for password authentication was removed on August 13, 2021.
On Tue, May 09, 2023 at 09:47:45PM -0600, William Torrez Corea wrote:
> Command:
>
> git push master origin
> >
>
> I want upload my change to branch MAIN but when i want upload my change i
> get the following error:
>
> remote: Support for password authentication was removed on August 13, 2021.
On Tue, 9 May 2023, William Torrez Corea wrote:
Command:
git push master origin
shouldn't that be git push origin master? Or even origin main?
I want upload my change to branch MAIN but when i want upload my change i
get the following error:
remote: Support for password authentication wa
On Sun, Mar 05, 2023 at 09:05:01AM +0100, john doe wrote:
> On 3/5/23 04:59, William Torrez Corea wrote:
> > I am working with remotes, when i want push to the remote with this command
>
> What CMD?
>
> > appear the following error:
> >
> > *git push main master*
>
> This error looks to indicat
On Sat, Mar 04, 2023 at 11:13:04PM -0500, Larry Martell wrote:
> On Sat, Mar 4, 2023 at 11:00 PM William Torrez Corea wrote:
>
> > I am working with remotes, when i want push to the remote with this
> > command appear the following error:
> >
> > *git push main master*
> >
> > fatal: 'main' does
On 3/5/23 04:59, William Torrez Corea wrote:
I am working with remotes, when i want push to the remote with this command
What CMD?
appear the following error:
*git push main master*
This error looks to indicate that you are pushing to main and master
branches.
fatal: 'main' does not app
On Sat, Mar 04, 2023 at 09:59:29PM -0600, William Torrez Corea wrote:
> I am working with remotes, when i want push to the remote with this command
> appear the following error:
>
> *git push main master*
>
> fatal: 'main' does not appear to be a git repository
> > fatal: Could not read from remo
On Sat, Mar 4, 2023 at 11:00 PM William Torrez Corea
wrote:
> I am working with remotes, when i want push to the remote with this
> command appear the following error:
>
> *git push main master*
>
> fatal: 'main' does not appear to be a git repository
>> fatal: Could not read from remote reposito
On Fri, Nov 26, 2021, 7:57 AM Harald Dunkel wrote:
> Hi folks,
>
> trying to build git 2.34.0-1 for bullseye I get 2 segfaults (see #991214).
> Apparently they pop up during the built-in tests, so I wonder if this is a
> FTBFS? If this is nothing to worry about, how comes that these segfaults
> a
On Sat, Jul 14, 2018 at 07:59:12PM +1000, Zenaan Harkness wrote:
> sound-theme-freedesktop spice-client-glib-usb-acl-helper tla tla-doc
Wow, tla - that's from either old-old-stable or old-old-old-stable :)
Shows how good Debian is at dist-upgrade. Dat's some dang fine
upgradin', bro!
Methinks it
On Fri, Jul 13, 2018 at 08:26:53AM -0400, Greg Wooledge wrote:
> > > that's what should be relevant here. Having libgnutls-deb0-28 installed
> > > (or not installed) should not matter at all.
> >
> > Well as I highlighted in another email above in this thread, when I
> > try to remove it, it want
On Fri 13 Jul 2018 at 10:50:18 (+), davidson wrote:
> On Wed, 11 Jul 2018, Zenaan Harkness wrote:
>
> Hellow Zenaan!
>
> >On Wed, Jul 11, 2018 at 11:32:30AM +0200, john doe wrote:
> >>On 7/11/2018 11:12 AM, Zenaan Harkness wrote:
> >>>Anyone know why git is failing to clone with the HTTPS pro
> > that's what should be relevant here. Having libgnutls-deb0-28 installed
> > (or not installed) should not matter at all.
>
> Well as I highlighted in another email above in this thread, when I
> try to remove it, it wants to rip out over 100 packages and over 500
> MiB's of Debian software.
On Fri, 13 Jul 2018, davidson wrote:
On Wed, 11 Jul 2018, Zenaan Harkness wrote:
Hellow Zenaan!
On Wed, Jul 11, 2018 at 11:32:30AM +0200, john doe wrote:
On 7/11/2018 11:12 AM, Zenaan Harkness wrote:
[snip]
OK so that page suggests reinstalling package libgnutls-deb0-28
Err... maybe it'
On Wed, 11 Jul 2018, Zenaan Harkness wrote:
Hellow Zenaan!
On Wed, Jul 11, 2018 at 11:32:30AM +0200, john doe wrote:
On 7/11/2018 11:12 AM, Zenaan Harkness wrote:
Anyone know why git is failing to clone with the HTTPS protocol (but
succeeds with the git protocol)?
Example:
$ git clone https
On Thu, Jul 12, 2018 at 08:24:35AM -0400, Greg Wooledge wrote:
> On Thu, Jul 12, 2018 at 05:45:46AM +1000, Zenaan Harkness wrote:
> > On Wed, Jul 11, 2018 at 08:30:51AM -0400, Greg Wooledge wrote:
> > > On Wed, Jul 11, 2018 at 09:48:10PM +1000, Zenaan Harkness wrote:
> > > > Why is this package mis
On Thu, Jul 12, 2018 at 05:45:46AM +1000, Zenaan Harkness wrote:
> On Wed, Jul 11, 2018 at 08:30:51AM -0400, Greg Wooledge wrote:
> > On Wed, Jul 11, 2018 at 09:48:10PM +1000, Zenaan Harkness wrote:
> > > Why is this package missing from the repos, but installed in my
> > > stretch install?
> >
>
On Wed, Jul 11, 2018 at 08:30:51AM -0400, Greg Wooledge wrote:
> On Wed, Jul 11, 2018 at 09:48:10PM +1000, Zenaan Harkness wrote:
> > Why is this package missing from the repos, but installed in my
> > stretch install?
>
> Because you upgraded from jessie. This lets you keep older shared
> librar
On Wed, Jul 11, 2018 at 09:48:10PM +1000, Zenaan Harkness wrote:
> Why is this package missing from the repos, but installed in my
> stretch install?
Because you upgraded from jessie. This lets you keep older shared
libraries or other packages as long as they don't conflict with anything
in stret
On Wed, Jul 11, 2018 at 01:37:44PM +0200, john doe wrote:
> On 7/11/2018 12:37 PM, Zenaan Harkness wrote:
> > On Wed, Jul 11, 2018 at 11:32:30AM +0200, john doe wrote:
> > > On 7/11/2018 11:12 AM, Zenaan Harkness wrote:
> > > > Anyone know why git is failing to clone with the HTTPS protocol (but
>
On 7/11/2018 12:37 PM, Zenaan Harkness wrote:
On Wed, Jul 11, 2018 at 11:32:30AM +0200, john doe wrote:
On 7/11/2018 11:12 AM, Zenaan Harkness wrote:
Anyone know why git is failing to clone with the HTTPS protocol (but
succeeds with the git protocol)?
Example:
$ git clone https://github.com/g
On Wed, Jul 11, 2018 at 11:32:30AM +0200, john doe wrote:
> On 7/11/2018 11:12 AM, Zenaan Harkness wrote:
> > Anyone know why git is failing to clone with the HTTPS protocol (but
> > succeeds with the git protocol)?
> >
> > Example:
> >
> > $ git clone https://github.com/gnubee-git/GnuBee_Docs.gi
On 7/11/2018 11:12 AM, Zenaan Harkness wrote:
Anyone know why git is failing to clone with the HTTPS protocol (but
succeeds with the git protocol)?
Example:
$ git clone https://github.com/gnubee-git/GnuBee_Docs.git docs.gits
Cloning into 'docs.gits'...
fatal: unable to access
'https://github.co
On Jo, 06 nov 14, 20:08:50, basti wrote:
> Hello,
> I know that this can be a bit off-topic.
> When I try to build a package based on git and use
>
> git-buildpackage => docs are not include in deb-file.
> dpkg-buildpackage => docs ARE include in deb-file.
>
> dh_installdocs is included in rules
"Claes Wallin (韋嘉誠)" writes:
> On 06/09/14 06:04, lee wrote:
>> Hi,
>>
>> how would I figure out what the last commit to a remote repo was without
>> first fetching or pulling the remote repo?
>
> $ git ls-remote origin
>
> ... will show you the list of references (tags, branches/heads) that
> ex
On 06/09/14 06:04, lee wrote:
> Hi,
>
> how would I figure out what the last commit to a remote repo was without
> first fetching or pulling the remote repo?
$ git ls-remote origin
... will show you the list of references (tags, branches/heads) that
exist on the remote "origin", and what SHA1 the
Joel Rees writes:
>> 2014/09/21 12:15 "lee" :
>> If there were diffs shown, only the local diffs would show up.
>> [...]
>
> Because your branch and origin/master have diverged. (Talking about HEAD
> was misleading. I still get cvs/svn and git confused in this way. Sorry
> about that)
Afaik git
2014/09/21 12:15 "lee" :
>
> Joel Rees writes:
>
> > On Sun, Sep 21, 2014 at 3:43 AM, lee wrote:
> >> Joel Rees writes:
> >>
> >>> Well, your experience with git and mine are quite different.
> >>>
> >>> On Sat, Sep 20, 2014 at 11:15 PM, lee wrote:
> Joel Rees writes:
> [...]
> >>>
>
Joel Rees writes:
> On Sun, Sep 21, 2014 at 3:43 AM, lee wrote:
>> Joel Rees writes:
>>
>>> Well, your experience with git and mine are quite different.
>>>
>>> On Sat, Sep 20, 2014 at 11:15 PM, lee wrote:
Joel Rees writes:
[...]
>>>
>>> Let's clear the conversation, it's too clutte
On Sun, Sep 21, 2014 at 3:43 AM, lee wrote:
> Joel Rees writes:
>
>> Well, your experience with git and mine are quite different.
>>
>> On Sat, Sep 20, 2014 at 11:15 PM, lee wrote:
>>> Joel Rees writes:
>>> [...]
>>
>> Let's clear the conversation, it's too cluttered for me to make sense
>> of
Joel Rees writes:
> Well, your experience with git and mine are quite different.
>
> On Sat, Sep 20, 2014 at 11:15 PM, lee wrote:
>> Joel Rees writes:
>> [...]
>
> Let's clear the conversation, it's too cluttered for me to make sense
> of it any more.
>
> cd to your local copy of the repository
Well, your experience with git and mine are quite different.
On Sat, Sep 20, 2014 at 11:15 PM, lee wrote:
> Joel Rees writes:
> [...]
Let's clear the conversation, it's too cluttered for me to make sense
of it any more.
cd to your local copy of the repository you want to do some work in.
Try t
Joel Rees writes:
> 2014/09/19 5:27 "lee" :
>>
>> Joel Rees writes:
>>
>> > On Sun, Sep 14, 2014 at 10:43 PM, lee wrote:
>> >> Joel Rees writes:
>> >
>> > Hmm. So. When you do a
>> >
>> > git status
>> >
>> > on the command line, with the current working directory at the
>> > appropriate p
2014/09/19 5:27 "lee" :
>
> Joel Rees writes:
>
> > On Sun, Sep 14, 2014 at 10:43 PM, lee wrote:
> >> Joel Rees writes:
> >>
> >>> 2014/09/14 6:55 "lee" yun.yagibdah.de
> >>> >:
>
> Joel Rees @
gmail.com
> >>> > writes:
> >>>
> >>> I can't think of any reason it would be dependent on
Joel Rees writes:
> On Sun, Sep 14, 2014 at 10:43 PM, lee wrote:
>> Joel Rees writes:
>>
>>> 2014/09/14 6:55 "lee" yun.yagibdah.de
>>> >:
Joel Rees @ gmail.com
>>> > writes:
>>>
>>> I can't think of any reason it would be dependent on https connectivity.
>>> Any way you can reach the
On Sun, Sep 14, 2014 at 10:43 PM, lee wrote:
> Joel Rees writes:
>
>> 2014/09/14 6:55 "lee" yun.yagibdah.de
>> >:
>>>
>>> Joel Rees @ gmail.com
>> > writes:
>>>
>>> > 2014/09/12 3:35 "lee" yun.yagibdah.de
>> >:
>>> >>
>>> >> [...]
>>> >> Well, I don't want to program some sort of meta-git ... I
Joel Rees writes:
> 2014/09/14 6:55 "lee" yun.yagibdah.de
> >:
>>
>> Joel Rees @ gmail.com
> > writes:
>>
>> > 2014/09/12 3:35 "lee" yun.yagibdah.de
> >:
>> >>
>> >> [...]
>> >> Well, I don't want to program some sort of meta-git ... I merely want
> a
>> >> simple way to be informed about new co
2014/09/14 6:55 "lee" yun.yagibdah.de
>:
>
> Joel Rees @ gmail.com
> writes:
>
> > 2014/09/12 3:35 "lee" yun.yagibdah.de
>:
> >>
> >> [...]
> >> Well, I don't want to program some sort of meta-git ... I merely want
a
> >> simple way to be informed about new commits.
> >
> > I'm still wondering whe
Joel Rees writes:
> 2014/09/12 3:35 "lee" :
>>
>> [...]
>> Well, I don't want to program some sort of meta-git ... I merely want a
>> simple way to be informed about new commits.
>
> I'm still wondering whether a cron job that does a status request on the
> head in question wouldn't be good enou
2014/09/12 3:35 "lee" :
>
> [...]
> Well, I don't want to program some sort of meta-git ... I merely want a
> simple way to be informed about new commits.
I'm still wondering whether a cron job that does a status request on the
head in question wouldn't be good enough.
Otherwise, you're asking t
Jonathan Dowland writes:
> On Tue, Sep 09, 2014 at 10:05:33PM +0200, lee wrote:
>> I'm receiving 226542 bytes in 355 lines when I do this for one of the
>> repos ... and same for another one:
>>
>> curl https://github.com/lee-/info/git-newer/refs?service=git-upload-pack |
>> wc -cl
>
> I suspec
On Tue, Sep 09, 2014 at 10:05:33PM +0200, lee wrote:
> I'm receiving 226542 bytes in 355 lines when I do this for one of the
> repos ... and same for another one:
>
> curl https://github.com/lee-/info/git-newer/refs?service=git-upload-pack | wc
> -cl
I suspect the right URL should be
http://gi
On Monday, September 8, 2014 8:50:02 PM UTC+5:30, lee wrote:
> Rusi Mody writes:
> > On Monday, September 8, 2014 4:20:02 PM UTC+5:30, lee wrote:
> >> Jonathan Dowland writes:
> >> > On Sat, Sep 06, 2014 at 12:04:44AM +0200, lee wrote:
> >> >> how would I figure out what the last commit to a remot
Jonathan Dowland writes:
> On Mon, Sep 08, 2014 at 11:58:35PM +0200, lee wrote:
>> One is using git:, the other one https:.
> snip
>> I don't have ssh access to any of the remote hosts. Both repos, I can
>> only clone/fetch/merge from.
>
> OK.
>
>> But I don't want to fetch? If I can fetch only
On Tue, Sep 09, 2014 at 09:51:12AM +0100, Jonathan Dowland wrote:
> To persue this further, I'd suggest reading up on the git:// wire protocol
> (quite possibly there's a command other than 'git-upload-pack' which would
> give you what you want)
P.S.: this is a pretty nice description of the wire
On Mon, Sep 08, 2014 at 11:58:35PM +0200, lee wrote:
> One is using git:, the other one https:.
snip
> I don't have ssh access to any of the remote hosts. Both repos, I can
> only clone/fetch/merge from.
OK.
> But I don't want to fetch? If I can fetch only the data (a minimal
> amount of data)
Jonathan Dowland writes:
> I've been thinking about how to answer your question properly and I realised
> that the answer probably depends on which protocol you are using to pull from
> the remote repo. Or more properly, which protocols the remote repo supports.
One is using git:, the other one
I've been thinking about how to answer your question properly and I realised
that the answer probably depends on which protocol you are using to pull from
the remote repo. Or more properly, which protocols the remote repo supports.
If it is listening as pure git://, or git+ssh://, then (at least i
Tony van der Hoff writes:
>> Why can't I simply ask the (server of the) remote repo "when/what was
>> the last commit?". Why should I have to transfer large or huge amounts
>> of data to get an information which doesn't need to take more than 4
>> bytes (i. e. a unix timestamp)?
>>
>>
> It see
Chris Bannister writes:
> On Mon, Sep 08, 2014 at 06:29:08PM +0200, lee wrote:
>> lee writes:
>>
>> > how would I figure out what the last commit to a remote repo was without
>> > first fetching or pulling the remote repo?
>>
>> For now, I'm going with 'git status'. See https://github.com/lee
On 08/09/14 15:10, lee wrote:
> Rusi Mody writes:
>
>> On Monday, September 8, 2014 4:20:02 PM UTC+5:30, lee wrote:
>>> Jonathan Dowland writes:
>>
On Sat, Sep 06, 2014 at 12:04:44AM +0200, lee wrote:
> how would I figure out what the last commit to a remote repo was without
> first
On Mon, Sep 08, 2014 at 06:29:08PM +0200, lee wrote:
> lee writes:
>
> > how would I figure out what the last commit to a remote repo was without
> > first fetching or pulling the remote repo?
>
> For now, I'm going with 'git status'. See https://github.com/lee-/git-newer
>
> I'd still like to
lee writes:
> how would I figure out what the last commit to a remote repo was without
> first fetching or pulling the remote repo?
For now, I'm going with 'git status'. See https://github.com/lee-/git-newer
I'd still like to have a better way to figure out if there have been new
commits ...
Joel Rees writes:
> On Mon, Sep 8, 2014 at 7:39 PM, lee wrote:
>> [...]
>> I have read so much documentation that I'm able to use git for what I'm
>> using it. If you are aware of some documentation that would be helpful
>> for the problem at hand, please feel free to point it out.
>
> How much
Rusi Mody writes:
> On Monday, September 8, 2014 4:20:02 PM UTC+5:30, lee wrote:
>> Jonathan Dowland writes:
>
>> > On Sat, Sep 06, 2014 at 12:04:44AM +0200, lee wrote:
>> >> how would I figure out what the last commit to a remote repo was without
>> >> first fetching or pulling the remote repo?
On Mon, Sep 8, 2014 at 7:39 PM, lee wrote:
> [...]
> I have read so much documentation that I'm able to use git for what I'm
> using it. If you are aware of some documentation that would be helpful
> for the problem at hand, please feel free to point it out.
How much have you read of this:
On Monday, September 8, 2014 4:20:02 PM UTC+5:30, lee wrote:
> Jonathan Dowland writes:
> > On Sat, Sep 06, 2014 at 12:04:44AM +0200, lee wrote:
> >> how would I figure out what the last commit to a remote repo was without
> >> first fetching or pulling the remote repo?
> > This is an interesting
Joel Rees writes:
> 2014/09/08 2:08 "lee" :
>>
>> Sven Joachim writes:
>>
>> >> Does this mean that I cannot rely on any of the output of 'git status'
>> >> to decide whether there were commits or not?
>> >
>> > Commits where, on your local branch or on the remote one?
>>
>> On the remote branch
Jonathan Dowland writes:
> On Sat, Sep 06, 2014 at 12:04:44AM +0200, lee wrote:
>> how would I figure out what the last commit to a remote repo was without
>> first fetching or pulling the remote repo?
>
> This is an interesting question and I don't know the answer to it, perhaps it
> is not yet
1 - 100 of 162 matches
Mail list logo
