From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Access to Buildroot git via https
Date: Wed, 27 Jul 2016 21:31:46 +0000 [thread overview]
Message-ID: <1469655016.3002.2.camel@synopsys.com> (raw)
In-Reply-To: <87y44mx0qa.fsf@dell.be.48ers.dk>
Hi Peter, Thomas,
On Wed, 2016-07-27 at 22:52 +0200, Peter Korsgaard wrote:
> >
> > >
> > > >
> > > > >
> > > > > >
> > > > > > "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>
> ?> Hello,
> ?> On Wed, 27 Jul 2016 08:32:13 +0000, Alexey Brodkin wrote:
>
> ?>> I just noticed GitHub repo was not updated in 10 days.
> ?>> Is there a problem with it?
>
> ?> My mistake. Some time ago, someone (Romain?) reported that the new tags
> ?> were not pushed to the Github repository. So I changed the "git push"
> ?> in my script to "git push --tags". Except that this only seems to push
> ?> the tags, not the commits themselves when there are new commits but no
> ?> new tags.
>
> ?> So I'm now doing a "git push" *and* a "git push --tags". This should
> ?> hopefully fix the problem.
>
> I *think* you can use git push --all.
At least now GitHub tree matches?https://git.busybox.net/buildroot/.
Thanks a lot for a prompt fix!
-Alexey
next prev parent reply other threads:[~2016-07-27 21:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 8:44 [Buildroot] Access to Buildroot git via https Alexey Brodkin
2016-07-18 8:49 ` Thomas Petazzoni
2016-07-18 8:50 ` Alexey Brodkin
2016-07-19 4:57 ` Bernd Kuhls
2016-07-27 8:32 ` Alexey Brodkin
2016-07-27 20:25 ` Thomas Petazzoni
2016-07-27 20:52 ` Peter Korsgaard
2016-07-27 21:31 ` Alexey Brodkin [this message]
2016-07-19 6:28 ` Yann E. MORIN
2016-07-19 7:13 ` Thomas Petazzoni
2016-07-19 9:15 ` Alexey Brodkin
2016-08-03 19:48 ` Peter Korsgaard
2016-08-04 3:59 ` Alexey Brodkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1469655016.3002.2.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox