Sir,
I have tried to incorporate the changes suggested by you.
I request you to please check the new patch file and guide me if some more
improvement is needed to be done.
Thanks and Regards
Abhinav Jain
On Tue, Feb 20, 2018 at 8:27 PM, Abhinav Jain wrote:
> Sir,
>
> I will edit the current
On 20 February 2018 at 01:52, Chris Johns wrote:
> I have pushed this.
>
> Would it be possible to get a patch for the documentation?
>
Yes, sure. I just overlooked that. Thanks for reminding. (patch should be
included in my previous message)
--
Best regards,
MK
___
Sir,
I have gone through the code and tried to trace out where the error is
occurring. I also read about the git status command and the problem which I
was able to figure out from this was with the git status command only.
I discussed this with Chris sir and he suggested me to make a different
fun
Sir,
I will edit the current patch accordingly and will take care of this in the
future.
Thanks and Regards
Abhinav Jain
On Tue, Feb 20, 2018 at 7:31 PM, Gedare Bloom wrote:
> Oops, I should read my mail better. Thanks for breaking this out Chris.
> Abhinav,
>
> On Tue, Feb 20, 2018 at 1:12 AM
According to commit d30be3129e9681a74efc80ce241aaf3c3a5b0efe in
rtems-source-builder repo.
Signed-off-by: Maksim E. Kozlov
---
rsb/commands.rst | 7 +++
1 file changed, 7 insertions(+)
diff --git a/rsb/commands.rst b/rsb/commands.rst
index 3ef7772..ab338c1 100644
--- a/rsb/commands.rst
+++
On Tue, Feb 20, 2018 at 8:10 AM, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello Joel,
>
> for which sections is this patch? Do you have a code example and a GCC
> command line to create one of these sections?
>
Honestly I have been carrying that patch for 6 months and can't
Hello Joel,
for which sections is this patch? Do you have a code example and a GCC command
line to create one of these sections?
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
Oops, I should read my mail better. Thanks for breaking this out Chris. Abhinav,
On Tue, Feb 20, 2018 at 1:12 AM, Abhinav Jain wrote:
> Sir,
>
> I have attached the patch file with this mail. I have tried to follow all
> the conventions that were listed in the User Git page. I request you to
> pl
On Sun, Feb 18, 2018 at 3:19 AM, Abhinav Jain wrote:
> Sir,
>
> I have gone through the code concerning the issue raised. I also read about
> the working of git status command and the problem that I am able to figure
> out is that although the existing code is able to check whether the current
> p
